[Touch-packages] [Bug 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)
Tested openssh-client/bionic-proposed,now 1:7.6p1-4ubuntu0.7 and confirmed that group's and others' read permissions are now preserved. Write and execute permissions are still removed, that is, a umask of 0133 seems to be applied. ** 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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1966591 Title: ssh-keygen -R changes known_hosts file permissions (mode) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Fix Committed Status in openssh source package in Focal: Fix Committed Status in openssh source package in Impish: Fix Released Status in openssh source package in Jammy: Fix Released Bug description: [Impact] When using "ssh-keygen -R" to remove a host from "known_hosts" the command changes permissions on the file. This can cause problems particularly when used on the global "known_hosts" file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non-root users suddenly fail to SSH and it's not immediately obvious why. [Test Plan] The problem happens on Bionic and Focal. $ lxc launch ubuntu-daily:focal openssh-bug1966591 $ lxc shell openssh-bug1966591 # ssh-keyscan github.com > test_known_hosts # chmod 644 test_known_hosts # ssh-keygen -R github.com -f test_known_hosts # stat test_known_hosts ... Access: (0600/-rw---) ... ... [Where problems could occur] The upstream patch is very simple and it is unlikely that it will cause any regressions. An indirect problem that could occur is that users might expect to see a more strict set of permissions on a "known_hosts" file after using "ssh-keygen -R", but arguably this is not defined behaviour and should not be relied upon. Of course, there is always a (very) small risk of introducing problems when rebuilding packages using newer versions of its dependencies (especially on Bionic, because it's older). [Original Description] When I use ssh-keygen -R to remove a host from known_hosts it changes permissions on the file. This causes problems particularly when used on the global known hosts file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non- root users suddenly fail to SSH and it's not immediately obvious why. To reproduce: $ ssh-keyscan github.com >test_known_hosts $ chmod 741 test_known_hosts $ ssh-keygen -R github.com -f test_known_hosts $ stat test_known_hosts ... Access: (0600/-rw---) ... Expected behavior: file permissions remain unchanged (mode 0741 in this example). $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:7.6p1-4ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1966591/+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 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)
Thanks a lot! 0644 are really the important bits, so while the behavior is still "user-surprising" it shouldn't cause any practical problems for us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1966591 Title: ssh-keygen -R changes known_hosts file permissions (mode) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: In Progress Status in openssh source package in Focal: In Progress Status in openssh source package in Impish: Fix Released Status in openssh source package in Jammy: Fix Released Bug description: When I use ssh-keygen -R to remove a host from known_hosts it changes permissions on the file. This causes problems particularly when used on the global known hosts file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non- root users suddenly fail to SSH and it's not immediately obvious why. To reproduce: $ ssh-keyscan github.com >test_known_hosts $ chmod 741 test_known_hosts $ ssh-keygen -R github.com -f test_known_hosts $ stat test_known_hosts ... Access: (0600/-rw---) ... Expected behavior: file permissions remain unchanged (mode 0741 in this example). $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:7.6p1-4ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1966591/+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 1966591] [NEW] ssh-keygen -R changes known_hosts file permissions (mode)
Public bug reported: When I use ssh-keygen -R to remove a host from known_hosts it changes permissions on the file. This causes problems particularly when used on the global known hosts file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non-root users suddenly fail to SSH and it's not immediately obvious why. To reproduce: $ ssh-keyscan github.com >test_known_hosts $ chmod 741 test_known_hosts $ ssh-keygen -R github.com -f test_known_hosts $ stat test_known_hosts ... Access: (0600/-rw---) ... Expected behavior: file permissions remain unchanged (mode 0741 in this example). $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:7.6p1-4ubuntu0.6 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1966591 Title: ssh-keygen -R changes known_hosts file permissions (mode) Status in openssh package in Ubuntu: New Bug description: When I use ssh-keygen -R to remove a host from known_hosts it changes permissions on the file. This causes problems particularly when used on the global known hosts file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non- root users suddenly fail to SSH and it's not immediately obvious why. To reproduce: $ ssh-keyscan github.com >test_known_hosts $ chmod 741 test_known_hosts $ ssh-keygen -R github.com -f test_known_hosts $ stat test_known_hosts ... Access: (0600/-rw---) ... Expected behavior: file permissions remain unchanged (mode 0741 in this example). $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:7.6p1-4ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966591/+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 1935890] [NEW] package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: avahi-utils 0.7-4ubuntu7.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: avahi-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 11 06:22:50 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2021-05-13 (60 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: avahi Title: package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1935890 Title: package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным Status in avahi package in Ubuntu: New Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: avahi-utils 0.7-4ubuntu7.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: avahi-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 11 06:22:50 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2021-05-13 (60 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: avahi Title: package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1935890/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
@xnox, I think for bionic it may be possible to port changes from https://github.com/xapienz/curl-debian-scripts (branch ppa_bionic) into upstream ubuntu (currently debs are in PPA https://launchpad.net/~xapienz/+archive/ubuntu/curl34). I can't guarantee that such constructed binaries will work for all cases, but during the last 2.5 years I haven't got any complaints from PPA users. For focal - maybe it is already fixed, but I see that around 900 people are still using my PPA in focal, so maybe there are some apps which still require it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: Opinion Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
*** This bug is a duplicate of bug 1683383 *** https://bugs.launchpad.net/bugs/1683383 Same with Kubuntu 20. -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in Ubuntu MATE: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so
Okay, this happens. But I can't help but wonder why it wasn't deprecated first and why it still present in public headers then? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1883079 Title: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt- pkg.so Status in apt package in Ubuntu: Invalid Bug description: The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-pkg.so.6.0.0. nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap 001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) 0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, DynamicMMap**) 00167b10 T pkgCache::pkgCache(MMap*, bool) 00167b10 T pkgCache::pkgCache(MMap*, bool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so
nm -D -C libapt-pkg.so.5.0 | grep MMap (Ubuntu 18.04) ... 000c97d0 T MMap::Map(FileFd&) 000c9e10 T MMap::Sync(unsigned long, unsigned long) 000c9b80 T MMap::Sync() 000c9c20 T MMap::Close(bool) 000c97a0 T MMap::MMap(unsigned long) 000c9b40 T MMap::MMap(FileFd&, unsigned long) 000c97a0 T MMap::MMap(unsigned long) 000c9b40 T MMap::MMap(FileFd&, unsigned long) 000c9d20 T MMap::~MMap() 000c9d00 T MMap::~MMap() 000c9d00 T MMap::~MMap() ... ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1883079 Title: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt- pkg.so Status in apt package in Ubuntu: New Bug description: The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-pkg.so.6.0.0. nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap 001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) 0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, DynamicMMap**) 00167b10 T pkgCache::pkgCache(MMap*, bool) 00167b10 T pkgCache::pkgCache(MMap*, bool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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 1883079] [NEW] The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so
Public bug reported: The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt- pkg.so.6.0.0. nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap 001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) 0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, DynamicMMap**) 00167b10 T pkgCache::pkgCache(MMap*, bool) 00167b10 T pkgCache::pkgCache(MMap*, bool) ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1883079 Title: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt- pkg.so Status in apt package in Ubuntu: New Bug description: The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-pkg.so.6.0.0. nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap 001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) 0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, DynamicMMap**) 00167b10 T pkgCache::pkgCache(MMap*, bool) 00167b10 T pkgCache::pkgCache(MMap*, bool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so
cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1883079 Title: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt- pkg.so Status in apt package in Ubuntu: New Bug description: The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-pkg.so.6.0.0. nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap 001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) 0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, DynamicMMap**) 00167b10 T pkgCache::pkgCache(MMap*, bool) 00167b10 T pkgCache::pkgCache(MMap*, bool) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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 1812223] Re: gir test fail on ppc64el
Today on GitHub a ppc64el webhook was turned on for the systemd project. The fuzzers (built with ASan) crashed there as soon as they started with something like ``` 757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1) --- command --- /usr/bin/env /tmp/autopkgtest.vdKhS9/build.g6f/systemd/build-deb/fuzz-varlink:address /tmp/autopkgtest.vdKhS9/build.g6f/systemd/test/fuzz/fuzz-varlink/oss-fuzz-14708 --- stderr --- ==24171==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING. ==24171==ASan shadow was supposed to be located in the [0x01ff-0x11ff] range. ==24171==Process memory map follows: ``` https://github.com/systemd/systemd/pull/13568#issuecomment-545426488 I'm not sure what exactly is going on there but I'm wondering if anyone runs anything under ASan on ppc64el on a regular basis. Is it even supported there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812223 Title: gir test fail on ppc64el Status in Meson: New Status in gcc-8 package in Ubuntu: New Status in gobject-introspection package in Ubuntu: New Status in meson package in Ubuntu: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/m/meson/20190116_031026_4df33@/log.gz ninja explain: genmarshal/genmarshalprog is dirty [1/75] Generating simple-resources_c with a custom command. [2/75] Generating simple-resources_h with a custom command. [3/75] Generating res3 with a meson_exe.py custom command. [4/75] Compiling C object 'resources/41d311a@@simple-resources-test@exe/meson-generated_.._simple-resources.c.o'. [5/75] Compiling C object 'resources/41d311a@@simple-resources-test@exe/simple-main.c.o'. [6/75] Generating simple-resources_gresource with a custom command. [7/75] Generating generated-resources_c with a custom command. [8/75] Generating generated-resources_h with a custom command. [9/75] Linking target resources/simple-resources-test. [10/75] Compiling C object 'resources/41d311a@@generated-resources-test@exe/meson-generated_.._generated-resources.c.o'. [11/75] Generating build-resources_gresource with a custom command. [12/75] Compiling C object 'resources/41d311a@@generated-resources-test@exe/generated-main.c.o'. [13/75] Linking target resources/generated-resources-test. [14/75] Compiling C object 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/dep2.c.o'. [15/75] Linking target gir/dep1/dep2/libdep2lib.so. [16/75] Compiling C object 'gir/dep1/07d7481@@dep1lib@sha/dep1.c.o'. [17/75] Generating symbol file 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/libdep2lib.so.symbols'. [18/75] Linking target gir/dep1/libdep1lib.so. [19/75] Generating symbol file 'gir/dep1/07d7481@@dep1lib@sha/libdep1lib.so.symbols'. [20/75] Compiling C object 'gir/327a146@@gir_lib2@sha/meson-sample2.c.o'. [21/75] Linking target gir/libgir_lib2.so. [22/75] Generating gsettings-compile-schemas with a custom command. [23/75] Compiling C object 'schemas/fd70ea1@@schemaprog@exe/schemaprog.c.o'. [24/75] Linking target schemas/schemaprog. [25/75] Generating generated-gdbus.c with a custom command. [26/75] Generating generated-gdbus.h with a custom command. [27/75] Generating generated-gdbus-docbook with a custom command. [28/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/meson-generated_.._generated-gdbus.c.o'. [29/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/gdbusprog.c.o'. [30/75] Generating MesonDep2-1.0.gir with a custom command. g-ir-scanner: link: cc -o /tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0 /tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 -Wl,-rpath,/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -ldep2lib -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [31/75] Linking target gdbus/gdbus-test. [32/75] Generating MesonDep2-1.0.typelib with a custom command. [33/75] Generating enums.h with a meson_exe.py custom command. [34/75] Generating enums.c with a meson_exe.py custom command. [35/75] Compiling C object 'mkenums/75bf728@@enumprog1@exe/meson-generated_.._enums.c.o'. [36/75] Compiling C object 'mkenums/75bf728@@enumprog1@exe/meson-generated_.._main1.c.o'. [37/75] Linking target mkenums/enumprog1. [38/75] Generating MesonDep1-1.0.gir with a custom command. FAILED: gir/dep1/MesonDep1-1.0.gir /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include --no-libtool --namespace=MesonDep1 --nsversion=1.0 --warn-all --output gir/dep1/MesonDep1-1.0.gir --c-include=dep1.h '-I/tmp/autopkgtest.GpLQfj/build.Rq
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> it looks like @laney is listed there, which is probably appropriate (he has admin access to the test systems, while I don't) My understanding is that @laney can help with the infrastructure where the tests are run. What usually happens on Ubuntu CI for the most part has nothing to do with the infrastructure. I'd say it's pretty stable except that for about a month if I recall correctly it failed to report the statuses of PRs but it was fixed by @laney in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817344. Regarding TEST-34 on i386, could you open an issue on GitHub? It could probably be kept on the list as well until it's fixed. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
By the way, @ddstreet would it be OK to mention that you maintain Ubuntu CI at https://www.freedesktop.org/wiki/Software/systemd/autopkgtest/? Currently it's almost impossible to figure out who is responsible for it. At some point I assumed it was @xnox but it doesn't seem the case so I don't even try to cc @xnox any more. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Regarding i386, I downloaded the log and took a look at what failed there. Turns out all the tests except for TEST-34-DYNAMICUSERMIGRATE, where the global timeout kicked in, passed. Apparently, to judge from https://salsa.debian.org/systemd- team/systemd/blob/master/debian/tests/upstream, on Ubuntu CI the tests are still run one by one whereas on CentOS CI we started to run them in parallel back in March (https://github.com/systemd/systemd-centos- ci/pull/78) so it's no wonder the whole test times out sporadically. I don't expect the script in the Debian package to be fixed any time soon so could anyone either bump up the timeout or turn the test off? -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> Opened MR to blacklist TEST-15 and TEST-22 That PR on GitHub hasn't been merged yet so I think it's too soon to turn those tests off. > ah, ok - so I did look into this, or at least some failures really similar to this, a while back, for bug 1831468. As far as I can tell, several tests failed there because QEMU_TIMEOUT kicked in. It's different from what is going on on i386 on GitHub where the whole upstream test fails due to the global timeout. > Let me know if that sounds familiar or if you have any debugging suggestions Depending on where the test is run it could be 300s isn't enough for it to finish. Given that it's not particularly popular platform I assume it's run in VMs where the upstream test also launch VMs with QEMU with no acceleration whatsoever. Could you try bumping up QEMU_TIMEOUT to see whether it helps? -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Just to clarify, I think that it would be better to turn off the test globally because we know it's flaky and unstable and we generally never roll out globally flaky tests so as not to annoy contributors (I'm not sure why Ubuntu CI should be different from any other CI system we use upstream). And then, it should be possible to run the test over and over again somewhere to see what fails updating the list along the way. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 |
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Regarding the blacklist, we started to work on it in https://github.com/systemd/systemd/issues/11195 (which was initially about merging PRs where bugs were caught by Travis CI but ignored because everybody was used to Ubuntu CI failing more often than not) and ended up with a list of test I suggested because I more or less knew what was flaky at the time and kept monitoring Ubuntu CI for a couple of days. As far as I can tell, it has been abandoned since then. If you're ready to keep the list up to date by visiting PRs where Ubuntu CI fails I'm of course all for it. Other than that, right now the upstream test timeouts on i386, which has been on for just two days: https://github.com/systemd/systemd/pull/12901#issuecomment-506646998. I'm not sure how turning off some tests will help there (because generally I don't understand why it fails). Plus, in https://github.com/systemd/systemd/pull/12861#issuecomment-506556062 the test is completely broken on Ubuntu CI and I have no idea why. ** Bug watch added: github.com/systemd/systemd/issues #11195 https://github.com/systemd/systemd/issues/11195 -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
I agree ideally the test should be fixed but it's been flaky for a couple of years and I didn't notice anyone who would be willing to try to figure it out. I think it's time to admit nobody cares. Even if I'm totally wrong and someone is interested in getting it to work on Ubuntu CI, it should be possible to turn it off globally so as not to annoy contributors with known issues they shouldn't even have to care about and keep trying to reproduce it "locally" (as we do on CentOS CI, Travis CI, Azure Pipelines and so on and so forth). -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
In the meantime, I brought arm64 back almost as soon as https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was merged. It looks promising except that the "upstream" test is flaky there as well. It'd be great to turn it off on Ubuntu CI. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Good to know! Thank you! Would it also be possible to mark the "upstream" test (https://salsa.debian.org/systemd- team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it off altogether? We run it on CentOS and Arch anyway so it should be safe. On Ubuntu CI it's particularly flaky and I don't think it makes much sense to keep running it there until some stuff like timeouts isn't adjusted to VMs on the Ubuntu CI infrastructure. I think at this point it would make sense to make sure that Ubuntu-specific tests are in good shape. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tena
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> looks like this has been fixed already upstream Yes. I merged the PR (created by @yuwata) fixing that this morning. > looks like someone stopped that; it's only running tests for 12888, 12897, and 12899 currently. In https://github.com/systemd/systemd/issues/12891#issuecomment-506093934 I asked Iain Lane to stop that, which I think explains why it's not there any more. > I'll take a look at those failures. Those failures most likely have something to do with that PR and probably should be fixed upstream. I think it would be better to somehow address https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864. arm64 has been off since December 2018 due to that 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup |
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
By the way, judging by http://autopkgtest.ubuntu.com/running#pkg- systemd-upstream, it seems Ubuntu CI keeps running the tests for PR 12618, which was merged about a month ago. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524250971084851b3792a68fbc398dd
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Anyway, as I said in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/comments/3, I don't think Ubuntu CI in its current form is suitable for CI so I'll just turn it off as soon as it starts failing again. I'm afraid I don't have time for keeping an eye on it and reporting whatever comes up there on bugs.launchpad.net. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
I turned on bionic-amd64 and bionic-i386 yesterday. VMs no longer fail to boot but apparently something else was broken on bionic-i386 while it was off: https://github.com/systemd/systemd/issues/12891. In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351 both bionic-amd64 and bionic-s390x failed due to something weird I don't quite understand. It would be great if someone who is interested in keeping it afloat could chime in there to help to debug that. ** Bug watch added: github.com/systemd/systemd/issues #12891 https://github.com/systemd/systemd/issues/12891 -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE
[Touch-packages] [Bug 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
I'd add that it seems to me the "upstream" mode of Ubuntu CI doesn't seem to be actively maintained because unlike the other CI systems used upstream (which are usually fixed almost immediately), it can be broken for weeks (or sometimes even months) which isn't suitable for CI. In principle, if nobody takes care of it, it would probably makes sense to turn off Ubuntu CI upstream (which I did) and switch to the usual release cycle where maintainers try to release the package, catch a lot of bugs (easily preventable by the CI when PRs are opened) and report them upstream. It's far from ideal, of course, but I don't know what else to do about it. -- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: New Status in systemd source package in Eoan: New Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
That's correct. The assertion is at https://salsa.debian.org/systemd- team/systemd/blob/master/debian/tests/boot-and-services#L421. Regarding which release of Ubuntu is affected, I have to say I don't know. The issue is mostly about "upstream" mode of Ubuntu CI, which can be detected by checking an environment variable called TEST_UPSTREAM, as far as I can remember. -- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: New Status in systemd source package in Eoan: New Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1831296] [NEW] __main__.SeccompTest is failing on Ubuntu CI
Public bug reported: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: New Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1829829] Re: Ubuntu CI has been flaky for a week
To judge from https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_185445_b37c3@/log.gz, VMs seems to also be throwing kernel panics: ``` [0.894903] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [0.895921] EDD information not available. [0.985183] isapnp: No Plug & Play device found [0.986013] md: Waiting for all devices to be available before autodetect [0.987166] md: If you don't use raid, use raid=noautodetect [0.988330] md: Autodetecting RAID arrays. [0.989038] md: autorun ... [0.989525] md: ... autorun DONE. [0.990139] VFS: Cannot open root device "UUID=961ce78b-c06e-4632-9aa0-56a8356b081b" or unknown-block(0,0): error -6 [0.991923] Please append a correct "root=" boot option; here are the available partitions: [0.993406] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.994818] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-50-generic #54-Ubuntu [0.996121] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [0.997704] Call Trace: [0.998138] dump_stack+0x58/0x81 [0.998713] panic+0x94/0x1e6 [0.999233] mount_block_root+0x199/0x234 [1.000111] ? calibrate_delay+0x190/0x4e0 [1.000833] ? create_dev.constprop.7+0x3a/0x53 [1.001611] mount_root+0x33/0x35 [1.002182] prepare_namespace+0x11b/0x167 [1.002885] kernel_init_freeable+0x1b3/0x1c5 [1.003634] ? rest_init+0xa0/0xa0 [1.004238] kernel_init+0xd/0x100 [1.004830] ret_from_fork+0x1c/0x38 [1.005892] Kernel Offset: 0x1000 from 0xc100 (relocation range: 0xc000-0xdf5fdfff) [1.007376] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` And there is another one at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_100015_69099@/log.gz ``` [ 41.006515] IP: rollback_registered_many+0x141/0x390 [ 41.007872] *pdpt = 1da0b001 *pde = [ 41.009424] Oops: 0002 [#1] SMP PTI [ 41.010396] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 floppy [ 41.017754] CPU: 0 PID: 85 Comm: kworker/u2:2 Not tainted 4.15.0-50-generic #54-Ubuntu [ 41.019883] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 41.022385] Workqueue: netns cleanup_net [ 41.023459] EIP: rollback_registered_many+0x141/0x390 [ 41.024825] EFLAGS: 00010202 CPU: 0 [ 41.025783] EAX: 0008 EBX: 0008 ECX: 0020 EDX: [ 41.027477] ESI: dae31ec4 EDI: 00ff EBP: dae31eac ESP: dae31e88 [ 41.029162] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.030641] CR0: 80050033 CR2: dfc746c0 CR3: 1da28000 CR4: 001406f0 [ 41.032333] Call Trace: [ 41.033030] ? netdev_run_todo+0x4a/0x300 [ 41.034136] unregister_netdevice_many.part.104+0x10/0x80 [ 41.035603] default_device_exit_batch+0x13c/0x160 [ 41.036933] ? do_wait_intr_irq+0x80/0x80 [ 41.038034] ops_exit_list.isra.8+0x53/0x60 [ 41.039169] cleanup_net+0x18e/0x260 [ 41.040152] process_one_work+0x1b9/0x3d0 [ 41.041246] worker_thread+0x37/0x420 [ 41.042254] kthread+0xf0/0x110 [ 41.043115] ? process_one_work+0x3d0/0x3d0 [ 41.044256] ? kthread_create_worker_on_cpu+0x20/0x20 [ 41.045640] ret_from_fork+0x2e/0x38 [ 41.046629] Code: ce d6 89 d8 03 0c 9d c0 34 bc d6 e8 5a d5 92 ff 89 d8 ba a0 e2 ce d6 e8 de de 11 00 3b 05 fc e3 ce d6 89 c3 72 d4 bf ff ff ff 00 <00> 00 00 00 00 00 00 00 00 01 00 ff ff ff ff ff ff fa 16 3e bb [ 41.051663] EIP: rollback_registered_many+0x141/0x390 SS:ESP: 0068:dae31e88 [ 41.053543] CR2: 0008 [ 41.054464] ---[ end trace 06d0534c6301b91d ]--- [ 41.057078] BUG: unable to handle kernel NULL pointer dereference at [ 41.059059] IP: flush_backlog+0x3f/0x120 [ 41.060132] *pdpt = 1da0b001 *pde = [ 41.061682] Oops: [#2] SMP PTI [ 41.062649] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 floppy [ 41.069990] CPU: 0 PID: 149 Comm: kworker/0:1H Tainted: G D 4.15.0-50-generic #54-Ubuntu [ 41.072469] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 41.074954] Workqueue: events_highpri flush_backlo
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
@pitti would it be possible to temporarily skip the tests where VMs are rebooted to reduce the blast radius so to speak? I really don't want to turn Ubuntu CI off completely. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: New Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524250971084851b3792a68fbc398dd |
[Touch-packages] [Bug 1829829] [NEW] Ubuntu CI has been flaky for a week
Public bug reported: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524250971084851b3792a68fbc398dd | +--++ --- : failure: Timed out on waiting for ssh connection autopkgtest [07:07:45]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe ``` Though judging by https://github.com/systemd/systemd/pull/12626, it appears that sometimes the tests pass. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New --
[Touch-packages] [Bug 1819589] [NEW] Ubuntu CI is broken
Public bug reported: Since https://salsa.debian.org/systemd-team/systemd/commit/8d810fda9a640a932d6e7b32afd958fe75e36f5b was merged Ubuntu CI has been failing with ``` Investigating (0) udev:amd64 < 237-3ubuntu10.13 -> 241-608-gfd541a5f08-0 @ii pumU Ib > Broken udev:amd64 Depends on dpkg:amd64 < 1.19.0.5ubuntu2.1 @ii mK > (>= 1.19.3) Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: udev : Depends: dpkg (>= 1.19.3) but 1.19.0.5ubuntu2.1 is to be installed W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. blame: https://salsa.debian.org/systemd-team/systemd.git badpkg: installation of basic binaries failed, exit code 100 autopkgtest [18:37:50]: ERROR: erroneous package: installation of basic binaries failed, exit code 100 Exit request sent.^M Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)... Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)... ``` It's also being discussed in https://github.com/systemd/systemd/pull/11963. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1819589 Title: Ubuntu CI is broken Status in systemd package in Ubuntu: New Bug description: Since https://salsa.debian.org/systemd-team/systemd/commit/8d810fda9a640a932d6e7b32afd958fe75e36f5b was merged Ubuntu CI has been failing with ``` Investigating (0) udev:amd64 < 237-3ubuntu10.13 -> 241-608-gfd541a5f08-0 @ii pumU Ib > Broken udev:amd64 Depends on dpkg:amd64 < 1.19.0.5ubuntu2.1 @ii mK > (>= 1.19.3) Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: udev : Depends: dpkg (>= 1.19.3) but 1.19.0.5ubuntu2.1 is to be installed W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. blame: https://salsa.debian.org/systemd-team/systemd.git badpkg: installation of basic binaries failed, exit code 100 autopkgtest [18:37:50]: ERROR: erroneous package: installation of basic binaries failed, exit code 100 Exit request sent.^M Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)... Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)... ``` It's also being discussed in https://github.com/systemd/systemd/pull/11963. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819589/+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 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1817344 Title: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results Status in autopkgtest package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I'm not sure this is the right place to report this, but apparently it's the best way to reach out to Dimitri John Ledkov (https://github.com/xnox) and Iain Lane (https://github.com/iainlane), who I believe at least know who maintains Ubuntu CI there. I'm copying the following verbatim from https://github.com/systemd/systemd/pull/11531#issuecomment-464731263 (where we are kind of discussing the issue): > The two PRs you referenced to fail in the `make check` unit tests (test-path). That's correct that test-path failed but it failed in https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported it in https://github.com/systemd/systemd/pull/11686 (that is, in https://github.com/systemd/systemd/pull/11686 in the logs for some reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something like that has happened often lately). In https://github.com/systemd/systemd/pull/11743#issuecomment-464637797, the issue is that Ubuntu CI showed the results for the first version of the PR (where there was a bug) and it didn't run the tests against the latest version. But in that case it's hard to tell because there is no way to figure out what exactly Ubuntu CI tested. That's why I asked @xnox to add `git describe` to https://salsa.debian.org/systemd- team/systemd/blob/master/debian/extra/checkout-upstream so that by looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it would be possible to find out what Ubuntu CI reports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1817344/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Hi Mark, The problem is a little more complex. For example, let's take package virtualbox-5.2 from official virtualbox repo (https://download.virtualbox.org/virtualbox/debian/). 1. Deb package depends on libcurl3. 2. Its binary is linked to library with name 'libcurl.so.4'. 3. Its binary requires existence of versioned symbols with names like 'curl_version_info@@CURL_OPENSSL_3'. 2 and 3 together don't allow simply solve the problem, because there are apps, which read library of version 4 and use API of version 3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I think Canonical should implement some solution like in #47 to support both ABIs and keep it supported for some time, because all other apps need some time to upgrade to libcurl4 (18.04 is LTS, so it looks like it shouldn't have been upgraded to libcurl4 until 18.10). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Hello César Bento Freire, This is not related to libcurl. But I would suggest you to download libxerces-c3.1 from ubuntu 17.10 repository and try to install it: https://packages.ubuntu.com/artful/libxerces-c3.1 amd64: http://mirrors.kernel.org/ubuntu/pool/universe/x/xerces-c/libxerces-c3.1_3.1.4+debian-2_amd64.deb i386: http://mirrors.kernel.org/ubuntu/pool/universe/x/xerces-c/libxerces-c3.1_3.1.4+debian-2_i386.deb This may require you to install further additional dependencies from ubuntu 17.10, or it may just work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1738479] [NEW] libimobile device doesn't see device and device reboots when I'm disconnecting it from computer device doesn't see device, device reboots when I'm disconnecting it
Public bug reported: Hi. My computer: (Lubuntu): evg@evg-Parallels-Virtual-Platform:$ uname -a Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux (Ubuntu): Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken I've successfully installed all libs from this document https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc . And device isn't visible when I'm trying to pair it using idevicepair pair command, but it appears in all connected device list. evg@evg-Parallels-Virtual-Platform:$ lsusb Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1 Bus 001 Device 002: ID 203a:fff9 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub evg@evg-Parallels-Virtual-Platform:$ idevicepair pair No device found, is it plugged in? I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on Ubuntu (16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my ipad reboots when I disconnecting it from computer. video with reboot (Reboot appears only on Ubuntu, not Lubuntu): https://youtu.be/8expDYVAW4o ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1738479 Title: libimobile device doesn't see device and device reboots when I'm disconnecting it from computer device doesn't see device, device reboots when I'm disconnecting it from computer Status in libimobiledevice package in Ubuntu: New Bug description: Hi. My computer: (Lubuntu): evg@evg-Parallels-Virtual-Platform:$ uname -a Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux (Ubuntu): Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken I've successfully installed all libs from this document https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc . And device isn't visible when I'm trying to pair it using idevicepair pair command, but it appears in all connected device list. evg@evg-Parallels-Virtual-Platform:$ lsusb Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1 Bus 001 Device 002: ID 203a:fff9 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub evg@evg-Parallels-Virtual-Platform:$ idevicepair pair No device found, is it plugged in? I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on Ubuntu (16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my ipad reboots when I disconnecting it from computer. video with reboot (Reboot appears only on Ubuntu, not Lubuntu): https://youtu.be/8expDYVAW4o To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1738479/+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 1665695] [NEW] OpenSSH PKCS#11 interface does not support ECC.
Public bug reported: OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard ssh-keygen -v -D /usr/lib/libeTPkcs11.so debug1: manufacturerID cryptokiVersion 2.20 libraryDescription libraryVersion 9.1 debug1: label manufacturerID model serial <> flags 0x60d C_GetAttributeValue failed: 18 debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa no keys cannot read public key from pkcs11 pkcs11-tool --module /usr/lib/libeTPkcs11.so -O ... Public Key Object; EC EC_POINT 256 bits EC_POINT: 04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc EC_PARAMS: 06082a8648ce3d030107 label: TestECCpair Usage: encrypt, verify, wrap There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728 release: Ubuntu 16.04.2 LTS openssh version: 7.2p2-4ubuntu2.1 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1665695 Title: OpenSSH PKCS#11 interface does not support ECC. Status in openssh package in Ubuntu: New Bug description: OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard ssh-keygen -v -D /usr/lib/libeTPkcs11.so debug1: manufacturerID cryptokiVersion 2.20 libraryDescription libraryVersion 9.1 debug1: label manufacturerID model serial <> flags 0x60d C_GetAttributeValue failed: 18 debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa no keys cannot read public key from pkcs11 pkcs11-tool --module /usr/lib/libeTPkcs11.so -O ... Public Key Object; EC EC_POINT 256 bits EC_POINT: 04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc EC_PARAMS: 06082a8648ce3d030107 label: TestECCpair Usage: encrypt, verify, wrap There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728 release: Ubuntu 16.04.2 LTS openssh version: 7.2p2-4ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1665695/+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 1636573] Re: xinit flooding syslog
I have the same problem & don't know what to do. Linux Mint 18.1 Kodi version: 2:17.0~git20170210.1529-final-0xenial Trying to get in third-party repo. Kodi's flooding into file /var/log/syslog >30gb of two strings: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. -- 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/1636573 Title: xinit flooding syslog Status in pyopenssl package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows (kodi is a media center): /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi- standalone -- :1 -nolisten tcp vt8 This used to work fine with Ubuntu 16.04, but since the upgrade to 16.10 lots of log messages are sent to syslog. They are all repetitions of the following two lines: Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. These messages amount to >200 GB per day, so this is eating up all the disk space. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Oct 25 18:41:22 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-06 (1753 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1636573/+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 1534541] Re: Dash doesn't accept input (appears frozen) after youtube scope auth
I have simmilar bug when exiting fullscreen mode on youtube. Everything freezes, but I still can move mouse and do ctrl+alt+f1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1534541 Title: Dash doesn't accept input (appears frozen) after youtube scope auth Status in Canonical System Image: Confirmed Status in Mir: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: 1. Make sure youtube scope is not favorited. 2. Remove Google account from Accounts settings. 3. Open youtube scope via Manage Dash 4. Hit the orange 'Log-in to..' button 5. Authenticate with google. 6. Wait till youtube results are refreshed. The dash appears frozen now. It doesn't crash though, in fact the process is running and the dash responds to the dbus signal which invalidates current scope and forces a refresh (tested with dbus-send --session --type=signal '/com/canonical/unity/scopes' com.canonical.unity.scopes.InvalidateResults string:'clickscope'). Note, the launcher as well as apps still receive input and work ok. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1534541/+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 1482990] Re: ld -lpython3.4 failed
** Changed in: python3.4 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/python3.4/+question/270210 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1482990 Title: ld -lpython3.4 failed Status in python3.4 package in Ubuntu: Invalid Bug description: #ld -lpython3.4 --verbose attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed attempt to open //usr/local/lib32/libpython3.4.so failed attempt to open //usr/local/lib32/libpython3.4.a failed attempt to open //lib32/libpython3.4.so failed attempt to open //lib32/libpython3.4.a failed attempt to open //usr/lib32/libpython3.4.so failed attempt to open //usr/lib32/libpython3.4.a failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed attempt to open //usr/local/lib/libpython3.4.so failed attempt to open //usr/local/lib/libpython3.4.a failed attempt to open //lib/i386-linux-gnu/libpython3.4.so failed attempt to open //lib/i386-linux-gnu/libpython3.4.a failed attempt to open //lib/libpython3.4.so failed attempt to open //lib/libpython3.4.a failed attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+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 1482990] Re: ld -lpython3.4 failed
libboost compilation failed because of a lack of libpython3.4.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1482990 Title: ld -lpython3.4 failed Status in python3.4 package in Ubuntu: New Bug description: #ld -lpython3.4 --verbose attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed attempt to open //usr/local/lib32/libpython3.4.so failed attempt to open //usr/local/lib32/libpython3.4.a failed attempt to open //lib32/libpython3.4.so failed attempt to open //lib32/libpython3.4.a failed attempt to open //usr/lib32/libpython3.4.so failed attempt to open //usr/lib32/libpython3.4.a failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed attempt to open //usr/local/lib/libpython3.4.so failed attempt to open //usr/local/lib/libpython3.4.a failed attempt to open //lib/i386-linux-gnu/libpython3.4.so failed attempt to open //lib/i386-linux-gnu/libpython3.4.a failed attempt to open //lib/libpython3.4.so failed attempt to open //lib/libpython3.4.a failed attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+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 1482990] [NEW] ld -lpython3.4 failed
Public bug reported: #ld -lpython3.4 --verbose attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed attempt to open //usr/local/lib32/libpython3.4.so failed attempt to open //usr/local/lib32/libpython3.4.a failed attempt to open //lib32/libpython3.4.so failed attempt to open //lib32/libpython3.4.a failed attempt to open //usr/lib32/libpython3.4.so failed attempt to open //usr/lib32/libpython3.4.a failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed attempt to open //usr/local/lib/libpython3.4.so failed attempt to open //usr/local/lib/libpython3.4.a failed attempt to open //lib/i386-linux-gnu/libpython3.4.so failed attempt to open //lib/i386-linux-gnu/libpython3.4.a failed attempt to open //lib/libpython3.4.so failed attempt to open //lib/libpython3.4.a failed attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed ** Affects: python3.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1482990 Title: ld -lpython3.4 failed Status in python3.4 package in Ubuntu: New Bug description: #ld -lpython3.4 --verbose attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed attempt to open //usr/local/lib32/libpython3.4.so failed attempt to open //usr/local/lib32/libpython3.4.a failed attempt to open //lib32/libpython3.4.so failed attempt to open //lib32/libpython3.4.a failed attempt to open //usr/lib32/libpython3.4.so failed attempt to open //usr/lib32/libpython3.4.a failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed attempt to open //usr/local/lib/libpython3.4.so failed attempt to open //usr/local/lib/libpython3.4.a failed attempt to open //lib/i386-linux-gnu/libpython3.4.so failed attempt to open //lib/i386-linux-gnu/libpython3.4.a failed attempt to open //lib/libpython3.4.so failed attempt to open //lib/libpython3.4.a failed attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+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 1482808] [NEW] timedatectl status prints old timezone
Public bug reported: # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-cache policy systemd-services systemd-services: Installed: 204-5ubuntu20.13 Candidate: 204-5ubuntu20.13 Version table: *** 204-5ubuntu20.13 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status # timedatectl status Local time: Sat 2015-08-08 01:09:36 UTC Universal time: Sat 2015-08-08 01:09:36 UTC Timezone: Etc/UTC (UTC, +) # echo 'Europe/Moscow' >/etc/timezone # dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Moscow' # timedatectl status Local time: Sat 2015-08-08 04:10:58 MSK Universal time: Sat 2015-08-08 01:10:58 UTC RTC time: Sat 2015-08-08 01:10:57 Timezone: Etc/UTC (MSK, +0300) # cat /etc/timezone Europe/Moscow Should be "Timezone: Europe/Moscow (MSK, +0300)" ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - timedatectl status prints timezone + timedatectl status prints old timezone -- 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/1482808 Title: timedatectl status prints old timezone Status in systemd package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 # apt-cache policy systemd-services systemd-services: Installed: 204-5ubuntu20.13 Candidate: 204-5ubuntu20.13 Version table: *** 204-5ubuntu20.13 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status # timedatectl status Local time: Sat 2015-08-08 01:09:36 UTC Universal time: Sat 2015-08-08 01:09:36 UTC Timezone: Etc/UTC (UTC, +) # echo 'Europe/Moscow' >/etc/timezone # dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Moscow' # timedatectl status Local time: Sat 2015-08-08 04:10:58 MSK Universal time: Sat 2015-08-08 01:10:58 UTC RTC time: Sat 2015-08-08 01:10:57 Timezone: Etc/UTC (MSK, +0300) # cat /etc/timezone Europe/Moscow Should be "Timezone: Europe/Moscow (MSK, +0300)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1482808/+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 1481871] [NEW] apt-key del doesn't understand fingerprint
Public bug reported: Description:Ubuntu 14.04.3 LTS Release:14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: - Installed: 1.0.1ubuntu2.10 + Installed: 1.0.1ubuntu2.10 - - apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 + apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 + 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise ** Description changed: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 - apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # - key is here + apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise ** Description changed: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key - apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # - key is still here + apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still + here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1481871 Title: apt-key del doesn't understand fingerprint Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1481871/+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