[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
Happens to me as well after upgrade from 19.04 to 19.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
#34 said: This bug affects a cryptographic (read: highly sensitive) feature, is 15 months old, a patch was proposed 12 months ago, but it is still of "Undecided" importance and still "Unassigned"? Come on! Are the ecryptfs-utils and systemd packages unmaintained at Ubuntu? Well, this bug is now over TWO YEARS old, and is still broken in 19.10. Expecting the systemd devs to care is, frankly, naive. I would have expected Canonical to at least do SOMETHING by now, even if it was just to add the keyctl hack to .profile, but that still leaves a ton of problems like non-root users never being unable to unmount their encrypted data - especially when you add in the OTHER systemd bugs that cause it to stay mounted and unencrypted even after logout. The problem here is that Kirkland was the one who was hot for ecryptfs, and he left Canonical a long time ago. While he may technically still be listed as the maintainer of the package, he clearly gives 0 f**ks about it. (He was still on Ubuntu staff when this bug first surfaced, and didn't even care THEN when it was literally (part of) his job, so it's no surprise he still doesn't now). The package needs to be demoted out of the repos, and the default behavior for encrypted /home changed to use something else - anything else, really - if it hasn't been already. In the meantime, the best thing you can do is just warn people not to use it, because at 2 years and counting I wouldn't hold my breath waiting for it to ever get sorted out... TLDR: use the keyctl hack from #26 to get your data back, then get the hell off ecryptfs as fast as possible. -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1851337] Re: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
Hi csozo, It looks like your system was under some form of memory pressure prior to the openssh installation. So I don't think this is a fault necessarily in openssh itself but rather due to your computer having run out of memory and gotten into some sort of inconsistent state. I would recommend rebooting the machine (if you haven't already), and running `apt-get -f install`. It looks like there might have been some reconfiguration questions (possibly updates to some of your manual configuration work?) so I'd run it from a terminal window and keep an eye on it. Once you've done that, can you let us know if the issue is resolved or if you get a better insight as to what went wrong? ** Description changed: I don't know. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: openssh-server 1:8.0p1-6build1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Tue Nov 5 08:22:46 2019 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-15 (293 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: sshd: no hostkeys available -- exiting. SourcePackage: openssh Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) - The dpkg log shows: + ... Setting up default-jre-headless (2:1.11-72) ... Setting up libpangoxft-1.0-0:amd64 (1.42.4-7) ... Setting up libqt4-network:amd64 (4:4.8.7+dfsg-7ubuntu3) ... Setting up openssh-server (1:8.0p1-6build1) ... Installing new version of config file /etc/ssh/moduli ... rescue-ssh.target is a disabled or a static unit, not starting it. Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server -Loaded: loaded (]8;;file://csozo-PC/lib/systemd/system/ssh.service/lib/systemd/system/ssh.service]8;;; enabled; vendor preset: enabled) -Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-05 08:22:46 CET; 6ms ago - Docs: ]8;;man:sshd(8)man:sshd(8)]8;; -]8;;man:sshd_config(5)man:sshd_config(5)]8;; - Process: 7160 ExecStartPre=/usr/sbin/sshd -t [0;1;31m(code=exited, status=1/FAILURE)[0m + Loaded: loaded (]8;;file://csozo-PC/lib/systemd/system/ssh.service/lib/systemd/system/ssh.service]8;;; enabled; vendor preset: enabled) + Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-05 08:22:46 CET; 6ms ago + Docs: ]8;;man:sshd(8)man:sshd(8)]8;; + ]8;;man:sshd_config(5)man:sshd_config(5)]8;; + Process: 7160 ExecStartPre=/usr/sbin/sshd -t [0;1;31m(code=exited, status=1/FAILURE)[0m dpkg: error processing package openssh-server (--configure): - installed openssh-server package post-installation script subprocess returned error exit status 1 + installed openssh-server package post-installation script subprocess returned error exit status 1 + + Apt ordering shows: + + ... + python-lockfile:amd64: Install + rygel:amd64: Install + xbrlapi:amd64: Install + NULL: ConfigurePending + + Dmesg indicates that an OOM killer event had occurred previously: + + [26198.228512] gsd-housekeepin invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 + [26198.228515] CPU: 0 PID: 4355 Comm: gsd-housekeepin Tainted: G OE 5.0.0-32-generic #34-Ubuntu + [26198.228515] Hardware name: System manufacturer System Product Name/H61M-K, BIOS 0801 07/21/2014 + [26198.228516] Call Trace: + [26198.228522] dump_stack+0x63/0x8a + [26198.228525] dump_header+0x54/0x2fb + [26198.228527] ? sched_clock+0x9/0x10 + [26198.228529] oom_kill_process.cold.30+0xb/0x1d6 + [26198.228530] out_of_memory+0x1c3/0x490 + [26198.228532] __alloc_pages_slowpath+0xb68/0xea0 + [26198.228534] __alloc_pages_nodemask+0x2c4/0x2e0 + [26198.228536] alloc_pages_current+0x81/0xe0 + [26198.228538] __page_cache_alloc+0x6a/0xa0 + [26198.228540] filemap_fault+0x3f0/0x8b0 + [26198.228541] ? filemap_map_pages+0x1ae/0x380 + [26198.228544] ext4_filemap_fault+0x31/0x44 + [26198.228546] __do_fault+0x3c/0x130 + [26198.228548] __handle_mm_fault+0xe4b/0x1280 + [26198.228550] ? __switch_to_asm+0x41/0x70 + [26198.228552]
[Touch-packages] [Bug 1851337] Re: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
** Description changed: I don't know. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: openssh-server 1:8.0p1-6build1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Tue Nov 5 08:22:46 2019 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-15 (293 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: - dpkg 1.19.7ubuntu2 - apt 1.9.4 + dpkg 1.19.7ubuntu2 + apt 1.9.4 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: sshd: no hostkeys available -- exiting. SourcePackage: openssh Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) + + + The dpkg log shows: + + Setting up default-jre-headless (2:1.11-72) ... + Setting up libpangoxft-1.0-0:amd64 (1.42.4-7) ... + Setting up libqt4-network:amd64 (4:4.8.7+dfsg-7ubuntu3) ... + Setting up openssh-server (1:8.0p1-6build1) ... + Installing new version of config file /etc/ssh/moduli ... + rescue-ssh.target is a disabled or a static unit, not starting it. + Job for ssh.service failed because the control process exited with error code. + See "systemctl status ssh.service" and "journalctl -xe" for details. + invoke-rc.d: initscript ssh, action "restart" failed. + ● ssh.service - OpenBSD Secure Shell server +Loaded: loaded (]8;;file://csozo-PC/lib/systemd/system/ssh.service/lib/systemd/system/ssh.service]8;;; enabled; vendor preset: enabled) +Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-05 08:22:46 CET; 6ms ago + Docs: ]8;;man:sshd(8)man:sshd(8)]8;; +]8;;man:sshd_config(5)man:sshd_config(5)]8;; + Process: 7160 ExecStartPre=/usr/sbin/sshd -t [0;1;31m(code=exited, status=1/FAILURE)[0m + dpkg: error processing package openssh-server (--configure): + installed openssh-server package post-installation script subprocess returned error exit status 1 -- 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/1851337 Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: openssh-server 1:8.0p1-6build1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Tue Nov 5 08:22:46 2019 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-15 (293 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: sshd: no hostkeys available -- exiting. SourcePackage: openssh Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) The dpkg log shows: ... Setting up default-jre-headless (2:1.11-72) ... Setting up libpangoxft-1.0-0:amd64 (1.42.4-7) ... Setting up libqt4-network:amd64 (4:4.8.7+dfsg-7ubuntu3) ... Setting up openssh-server (1:8.0p1-6build1) ... Installing new version of config file /etc/ssh/moduli ... rescue-ssh.target is a disabled or a static unit, not starting it. Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (]8;;file://csozo-PC/lib/systemd/system/ssh.service/lib/systemd/system/ssh.service]8;;; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-05 08:22:46 CET; 6ms ago Docs: ]8;;man:sshd(8)man:sshd(8)]8;;
[Touch-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
This bug was fixed in the package klibc - 2.0.7-1ubuntu4 --- klibc (2.0.7-1ubuntu4) focal; urgency=medium * Fix losetup, by switching to kernel uapi header, instead of buggy klibc one. LP: #1850184 -- Dimitri John Ledkov Thu, 07 Nov 2019 01:08:13 + ** Changed in: klibc (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Fix Released Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851453] Re: mir FTBFS in focal, blocks nettle transition
This is due to the new googletest 1.9 git snapshot in focal-proposed, which is (at least part way) through a big set of deprecations. If this needs to be pushed through urgently, we could evict googletest from focal-proposed, do the nettle transition, and then let googletest back in. I'll also keep working on making Mir build with the git snapshot gtest. Additionally we should probably update gtest to 1.10, which is an actual release ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1851453 Title: mir FTBFS in focal, blocks nettle transition Status in mir package in Ubuntu: New Bug description: a no-change rebuild of mir in focal has failed, for reasons that appear unrelated to nettle itself. [...] [ 61%] Linking CXX shared module ../../lib/client-modules/dummy.so cd /<>/build-amd64/tests/mir_test_framework && /usr/bin/cmake -E cmake_link_script CMakeFiles/mirclientplatformstub.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -Werror -Wno-psabi -ffat-lto-objects -Wno-error=null-dereference -Wno-error=overloaded-virtual -Wno-sign-compare -fno-lto -Dregister= -Wl,--version-script,/<>/tests/mir_test_framework/symbols-client.map -Wl,-Bsymbolic-fu nctions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -fuse-ld=gold -Wl,--no-undefined -shared -o ../../lib/client-modules/dummy.so CMakeFiles/mirclientplatformstub.dir/stub_client_platform_module.cpp.o -Wl,-rpath,/<>/build-amd64/lib: libmir-test-framework-static.a -lumockdev -lgobject-2.0 -lglib-2.0 -lumockdev -lgobject-2.0 -lglib-2.0 ../../lib/libmirserver.so.50 ../../lib/libmirplatform.so.16 ../../lib/libmirwayland.so.0 -lwayland-server ../../src/platforms/common/server/libserver_platform_common.a ../../src/platforms/common/server/kms-utils/libkms_utils.a -ldrm -ldrm /usr/lib/x86_64-linux-gnu/libEGL.so -lGLESv2 -lGLESv2 -lepoxy -lepoxy -ludev -ludev -lgio-2.0 -lgio-2.0 -luuid -luuid -lxcb -lxcb -lxcb-composite -lxcb-composite -lxcb-xfixes -lxcb-xfixes -lxcb-render -lxcb-render -lXcursor -lXcursor -llttng-ust -ldl -llttng-ust -latomic ../../lib/libmirclient.so.9 ../../lib/libmircommon.so.7 ../../src/capnproto/libmircapnproto.a /usr/lib/x86_64-linux-gnu/libcapnp-0.7.0.so /usr/lib/x86_64-linux-gnu/libkj-0.7.0.so -lpthread -pthread ../../lib/libmircore.so.1 -ldl ../../lib/libmirprotobuf.so.3 /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so ../../lib/libmircookie.so.2 -lnettle /usr/lib/x86_64-linux-gnu/libxkbcommon.so /usr/lib/x86_64-linux-gnu/libboost_date_time.so /usr/lib/x86_64-linux-gnu/libboost_system.so /usr/lib/x86_64-linux-gnu/libboost_program_options.so /usr/lib/x86_64-linux-gnu/libboost_filesystem.so /usr/lib/x86_64-linux-gnu/libboost_iostreams.so /usr/lib/x86_64-linux-gnu/libboost_regex.so /usr/lib/x86_64-linux-gnu/libgtest.a /usr/lib/x86_64-linux-gnu/libgtest_main.a /usr/lib/x86_64-linux-gnu/libgtest.a /usr/lib/x86_64-linux-gnu/libgtest_main.a ../../libGMock.a -lpthread -lgobject-2.0 -lglib-2.0 -lumockdev -lgobject-2.0 -lglib-2.0 /usr/src/gmock/src/gmock.cc:135: error: undefined reference to 'testing::Message::Message()' /usr/src/gmock/src/gmock.cc:135: error: undefined reference to 'testing::internal::ParseInt32(testing::Message const&, char const*, int*)' /usr/src/gmock/src/gmock-internal-utils.cc:181: error: undefined reference to 'testing::UnitTest::GetInstance()' /usr/src/gmock/src/gmock-internal-utils.cc:181: error: undefined reference to 'testing::internal::GetCurrentOsStackTraceExceptTop[abi:cxx11](testing::UnitTest*, int)' /usr/include/gtest/internal/gtest-port.h:1651: error: undefined reference to 'testing::internal::GTestLog::GTestLog(testing::internal::GTestLogSeverity, char const*, int)' /usr/include/gtest/internal/gtest-port.h:1651: error: undefined reference to 'testing::internal::GTestLog::~GTestLog()' [...] (https://launchpad.net/ubuntu/+source/mir/1.4.0-0ubuntu4/+build/18005823) This is holding up a mass of intertwined start-of-cycle library transitions in focal-proposed right now. Please fix this asap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1851453/+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 1834875] Re: cloud-init growpart race with udev
flock will not block inotify or udev events being emitted. See https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L322 https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L409 it will prevent udevd from running the rules against it. Thus effectively the event will be fired and done, but nothing actually executed for it. " /* apply rules, create node, symlinks */" Also, most importantly udevd also takes locks on devices, thus if one cannot take a lock on it, it means it shouldn't be touched yet as udevd is still processing it. Yeah, i read code and ioctls both call, and I have no idea which one is better, or what the difference is. If partx works, cool. But also, I thought udev should be updating partition tables all by itself. I somehow wonder if we even need partx call, if we properly flock the device and trigger udev after everything is done. Udev rules should be safe to be retriggered like that. But also, we should retrigger the expected events which have been skipped. So does growpart create partition? move it? delete/recreate one? i.e does ADD happen? or like REMOVE & ADD? or maybe it's like just MOVE or CHANGE? Do we have logs of the emitted events already? Don't like flags, as then we'll have to supported forever =) maybe env variable? or like simply change in focal and compare focal vs eoan? -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1851542] Re: autopkgtest fails due to aspell SRU
** Changed in: apport (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Status in apport source package in Disco:
New
Status in apport source package in Eoan:
Fix Committed
Bug description:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
==
FAIL: test_install_packages_versioned (__main__.T)
install_packages() with versions and with cache
--
Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in
test_install_packages_versioned
self.assertIn(result, 'aspell-doc version 1.1 required, but
0.60.7~20110707-3build1 is available\n')
AssertionError: 'aspell-doc version 1.1 required, but
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1
required, but 0.60.7~20110707-3build1 is available\n'
--
Ran 37 tests in 191.123s
FAILED (failures=1)
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1821376] Re: Report packages kept back by origins
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.12 --- unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:24:28 +0200 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821376 Title: Report packages kept back by origins Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+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 1821376] Re: Report packages kept back by origins
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.4 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:29:41 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821376 Title: Report packages kept back by origins Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+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 1821376] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821376 Title: Report packages kept back by origins Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+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 1821376] Re: Report packages kept back by origins
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2 --- unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) (LP: #1823070) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:22:02 +0200 ** Changed in: unattended-upgrades (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821376 Title: Report packages kept back by origins Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.4 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:29:41 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * MOTD does not go into details about upgradable packages being security fixes or just normal updates. * Users should be made aware if some of the security updates could not have been applied. * The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown. [Test Case] * The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly. * To test the fix manually: 1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades. 2. Observe MOTD messate showing the number of packages being kept back. [Regression Potential] * Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u. * It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command. [Original Bug Text] Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.12 --- unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:24:28 +0200 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * MOTD does not go into details about upgradable packages being security fixes or just normal updates. * Users should be made aware if some of the security updates could not have been applied. * The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown. [Test Case] * The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly. * To test the fix manually: 1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades. 2. Observe MOTD messate showing the number of packages being kept back. [Regression Potential] * Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u. * It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command. [Original Bug Text] Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.12 --- unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:24:28 +0200 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2 --- unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) (LP: #1823070) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:22:02 +0200 ** Changed in: unattended-upgrades (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * MOTD does not go into details about upgradable packages being security fixes or just normal updates. * Users should be made aware if some of the security updates could not have been applied. * The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown. [Test Case] * The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly. * To test the fix manually: 1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades. 2. Observe MOTD messate showing the number of packages being kept back. [Regression Potential] * Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u. * It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command. [Original Bug Text] Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1823070] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * MOTD does not go into details about upgradable packages being security fixes or just normal updates. * Users should be made aware if some of the security updates could not have been applied. * The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown. [Test Case] * The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly. * To test the fix manually: 1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades. 2. Observe MOTD messate showing the number of packages being kept back. [Regression Potential] * Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u. * It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command. [Original Bug Text] Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.4 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:29:41 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2 --- unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium * Report packages kept back by origin (LP: #1821376) * Store list of kept packages and report the number of them in motd (LP: #1823070) * Default to "/" as rootdir to fix saving list of kept packages. Thanks to Paul Wise (Closes: #932160) (LP: #1823070) * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Fri, 18 Oct 2019 13:22:02 +0200 ** Changed in: unattended-upgrades (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1848354] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
** Tags removed: block-proposed-bionic block-proposed-disco block- proposed-eoan block-proposed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
This bug was fixed in the package unattended-upgrades - 1.14ubuntu1.1 --- unattended-upgrades (1.14ubuntu1.1) eoan; urgency=medium * debian/tests/control: Mark upgrade-between-snapshots as flaky (Closes: #941752) (LP: #1848354) -- Balint Reczey Wed, 16 Oct 2019 17:47:42 +0200 ** Changed in: unattended-upgrades (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
"1 updates"? Having an "s" for 1 update is incorrect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * MOTD does not go into details about upgradable packages being security fixes or just normal updates. * Users should be made aware if some of the security updates could not have been applied. * The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown. [Test Case] * The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly. * To test the fix manually: 1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades. 2. Observe MOTD messate showing the number of packages being kept back. [Regression Potential] * Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u. * It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command. [Original Bug Text] Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
** Description changed: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. - http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html - http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html + https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html + https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: Fix Committed Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: Fix Committed Status in python3.7 source package in Eoan: Fix Committed Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
So this is actually happening now every time I lock my computer, no power change whatsoever (no standby, no suspend to RAM, no power off/reboot). So this is now becoming very frustrating to work with as I have to change my default audio device every time I use my computer now so that my volume controls (up/down) actually work. Can we PLEASE get this at least started to be looked at? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 540751] Re: Unable to use dead keys with java and ibus
Re-opening the ibus task for now. @Johny: This is a very old bug report, and a lot has been changed since it was originally filed. Any chance you can provide some details about how to reproduce the bug on 19.10? ** Changed in: ibus (Ubuntu) Status: Invalid => New ** Tags removed: lucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/540751 Title: Unable to use dead keys with java and ibus Status in ibus package in Ubuntu: New Status in openjdk-6 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Invalid Bug description: Using latest Lucid packages, I am unable to use ^ key to generate ê french character in every Java programs (jEdit, Netbeans, etc.). Typing ^ + e give just the e character. Typing ^ + Space and nothing appears. I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present. I've tried to remove ibus and everything works again (I've just unset XMODIFIERS and GTK_IM_MODULE). I don't know if it's an ibus bug or openjdk one. ProblemType: Bug Architecture: amd64 Date: Thu Mar 18 09:03:11 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java InstallationMedia: Error: [Errno 13] Permission non accordée: '/var/log/installer/media-info' NonfreeKernelModules: nvidia Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name SourcePackage: openjdk-6 Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/540751/+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 1851542] Re: autopkgtest fails due to aspell SRU
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Status in apport source package in Disco:
New
Status in apport source package in Eoan:
New
Bug description:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
==
FAIL: test_install_packages_versioned (__main__.T)
install_packages() with versions and with cache
--
Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in
test_install_packages_versioned
self.assertIn(result, 'aspell-doc version 1.1 required, but
0.60.7~20110707-3build1 is available\n')
AssertionError: 'aspell-doc version 1.1 required, but
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1
required, but 0.60.7~20110707-3build1 is available\n'
--
Ran 37 tests in 191.123s
FAILED (failures=1)
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1851542] Re: autopkgtest fails due to aspell SRU
** Description changed:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
+
+ ==
+ FAIL: test_install_packages_versioned (__main__.T)
+ install_packages() with versions and with cache
+ --
+ Traceback (most recent call last):
+ File "./test_backend_apt_dpkg.py", line 557, in
test_install_packages_versioned
+ self.assertIn(result, 'aspell-doc version 1.1 required, but
0.60.7~20110707-3build1 is available\n')
+ AssertionError: 'aspell-doc version 1.1 required, but
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1
required, but 0.60.7~20110707-3build1 is available\n'
+
+ --
+ Ran 37 tests in 191.123s
+
+ FAILED (failures=1)
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
-
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Status in apport source package in Disco:
New
Status in apport source package in Eoan:
New
Bug description:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
==
FAIL: test_install_packages_versioned (__main__.T)
install_packages() with versions and with cache
--
Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in
test_install_packages_versioned
self.assertIn(result, 'aspell-doc version 1.1 required, but
0.60.7~20110707-3build1 is available\n')
AssertionError: 'aspell-doc version 1.1 required, but
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1
required, but 0.60.7~20110707-3build1 is available\n'
--
Ran 37 tests in 191.123s
FAILED (failures=1)
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1848200] autopkgtest failure investigation
Stable Release Team,
I investigated the autopkgtest regression in Comment #12, and believe
it to not be a regression introduced by this gdb upload. apport has
been updated a couple of times via security since tests passed - and at
least one of those updates had known regressions. There is also a
false positive result due to an aspell SRU (see bug
1851542). Apparently autopkgtests don't run on security uploads by
default, so autopkgtest.ubuntu.com doesn't have apples/apples test
results to compare (prev-gdb/prev-apport vs. prev-gdb/new-apport). I
therefore ran some tests manually.
In the attached logs you'll see that:
- I am able to reproduce the same failures as the official
autopkgtests for apport
- The failures are the same with both the current gdb and the
bionic-proposed gdb
Therefore, please allow gdb to promulgate to -updates.
-dann
** Attachment added: "gdb.i386"
https://bugs.launchpad.net/bugs/1848200/+attachment/5303314/+files/gdb.i386
** Attachment added: "gdb.i386.proposed"
https://bugs.launchpad.net/bugs/1848200/+attachment/5303315/+files/gdb.i386.proposed
** Attachment added: "gdb.amd64"
https://bugs.launchpad.net/bugs/1848200/+attachment/5303316/+files/gdb.amd64
** Attachment added: "gdb.amd64.proposed"
https://bugs.launchpad.net/bugs/1848200/+attachment/5303317/+files/gdb.amd64.proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not stopping on breakpoint in a 32-bit program
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Bionic:
Fix Committed
Bug description:
[Impact]
After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
[Test Case]
This can be reproduced with a simple “hello world” program:
$ cat hello.c
#include
int main()
{
// printf() displays the string inside quotation
printf("Hello, World!");
return 0;
}
$ gcc -ggdb -m32 hello.c
$ gdb a.out
(gdb) b hello.c:5
Breakpoint 1 at 0x536: file hello.c, line 5.
(gdb) run
Starting program: /home/user/sandbox/a.out
warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
--- (and not stopping nor outputting the text…) ---
[Regression Risk]
Test case ran on arm64 and regression tested using the above test case on
amd64, i386 and s390x.
This regression was fixed on the upstream gdb-8.1 branch within a few
weeks of the breakage back in May 2018. Since then there have been no
other fixes in this area on that branch, implying this fixed the issue
and there were no further regressions discovered.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1851542] [NEW] autopkgtest fails due to aspell SRU
Public bug reported:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an aspell
SRU.
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: apport (Ubuntu Disco)
Importance: Undecided
Status: New
** Affects: apport (Ubuntu Eoan)
Importance: Undecided
Status: New
** Tags: block-proposed-bionic block-proposed-disco block-proposed-eoan
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Fix Released
** Tags added: block-proposed-disco
** Tags added: block-proposed-bionic block-proposed-eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Status in apport source package in Disco:
New
Status in apport source package in Eoan:
New
Bug description:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
** Description changed: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. - TODO: update after test rebuild - https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html - https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: Fix Committed Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: Fix Committed Status in python3.7 source package in Eoan: Fix Committed Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 540751] Re: Unable to use dead keys with java and ibus
This bug is now on Ubuntu 19.10 with openjdk-11... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/540751 Title: Unable to use dead keys with java and ibus Status in ibus package in Ubuntu: Invalid Status in openjdk-6 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Invalid Bug description: Using latest Lucid packages, I am unable to use ^ key to generate ê french character in every Java programs (jEdit, Netbeans, etc.). Typing ^ + e give just the e character. Typing ^ + Space and nothing appears. I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present. I've tried to remove ibus and everything works again (I've just unset XMODIFIERS and GTK_IM_MODULE). I don't know if it's an ibus bug or openjdk one. ProblemType: Bug Architecture: amd64 Date: Thu Mar 18 09:03:11 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java InstallationMedia: Error: [Errno 13] Permission non accordée: '/var/log/installer/media-info' NonfreeKernelModules: nvidia Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name SourcePackage: openjdk-6 Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/540751/+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 1834875] Re: cloud-init growpart race with udev
A couple of comments on the suggested path: > Imho the sequency of commands should be: > * take flock on the device, to neutralise udev +1 on this approach. Do you know if the flock will block systemd's inotify write watch on the block device which triggers udevd? This is the typical race we see with partition creation and rules executing. > * modify device with sfdisk > * reread partitions tables (i would say with blockdev --rereadpt, rather than > partx/partprobe) I'm not sure we can use blockdev --rereadpt as we are operating upon the root disk we're booted on and my understanding is that the ioctl that partx uses is the only way to update the kernel partition table while the disk is in use, otherwise we'd see the normal warning message like when you fdisk your booted device and it says the disk is busy and cannot read the partition table. > * release the flock +1 > * udevadm trigger --action=add --wait device (or trigger && settle) I don't relish the idea of *re-adding* actions on the disk again since the partx update should have already emitted the uevents associated with the new partitions. However, we could do this as a way to force reloading of everything. I'd like to withhold judgement on whether we need this after testing with use of flock on the device. > And like have a canary "only use locked codepath on this region" such that we can assert through testing that this no longer happens with new code, but does with old code. The change to cloud-utils growpart could add a flag (--use-flock) so cloud-init could emit different log messages on which path it takes (including a warning if we cannot use flock (ie, you may race). -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
@ Cloud init team, do we want to try changing cloud-utils to use a lock? And like have a canary "only use locked codepath on this region" such that we can assert through testing that this no longer happens with new code, but does with old code. -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
The same bug! ** Also affects: pulseaudio Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => datch (s-ogorodnick) ** No longer affects: pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1851063] Re: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)
As noted in the last comment I posted on this, I have managed to get the printer to work OK. Would it be possible to simplify/clarify somewhere what the different connections made by printers such as this are and mean? That is, when you plug this printer in, you get several 'printers' showing up in CUPS and in the Settings GUI. As some of them don't actually work, could they be either made to work or hidden in some way? BTW, the Ubuntu Debugging printer problems WIKI could usefully be changed to reflect that for a USB printer you shouldn't expect to see any /dev/usb/lp* at all (or at least that seems to be the case for this printer). ** Changed in: cups (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/cups/+question/685657 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851063 Title: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04) Status in cups package in Ubuntu: Invalid Bug description: [code] chris@chris-BlackTower:~$ lsmod | grep usb btusb 57344 0 btrtl 20480 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm snd_usb_audio 241664 4 snd_usbmidi_lib36864 1 snd_usb_audio snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_rawmidi36864 2 snd_seq_midi,snd_usbmidi_lib usblp 24576 0 snd_pcm 106496 4 snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd86016 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common usb_storage77824 3 uas usbhid 57344 0 hid 126976 2 usbhid,hid_generic chris@chris-BlackTower:~$ tail -f /var/log/syslog Nov 2 17:51:20 chris-BlackTower dbus-daemon[1927]: [session uid=1000 pid=1927] Successfully activated service 'org.gnome.Terminal' Nov 2 17:51:20 chris-BlackTower systemd[1910]: Started GNOME Terminal Server. Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Nov 2 17:51:22 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:51:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:52:17 chris-BlackTower kernel: [ 5451.623104] usb 1-2: USB disconnect, device number 5 Nov 2 17:52:25 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545188] audit: type=1400 audit(1572717167.836:71): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/sbin/route" pid=15859 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545588] audit: type=1400 audit(1572717167.836:72): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15860 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545989] audit: type=1400 audit(1572717167.836:73): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15861 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.424278] usb 1-2: new high-speed USB device number 6 using ehci-pci Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584559] usb 1-2: New USB device found, idVendor=04b8, idProduct=1109, bcdDevice= 1.00 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584565] usb 1-2: New USB device strings: Mfr=1,
[Touch-packages] [Bug 1851063] Re: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)
I have found a working combination of printer driver (from Epson) and printer definition (one plugged in it shows up about three times as different versions of the same XP-960), so this is not a 'bug'. Though I have to say that it's not immediately obviouw what is going on! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851063 Title: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04) Status in cups package in Ubuntu: Invalid Bug description: [code] chris@chris-BlackTower:~$ lsmod | grep usb btusb 57344 0 btrtl 20480 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm snd_usb_audio 241664 4 snd_usbmidi_lib36864 1 snd_usb_audio snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_rawmidi36864 2 snd_seq_midi,snd_usbmidi_lib usblp 24576 0 snd_pcm 106496 4 snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd86016 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common usb_storage77824 3 uas usbhid 57344 0 hid 126976 2 usbhid,hid_generic chris@chris-BlackTower:~$ tail -f /var/log/syslog Nov 2 17:51:20 chris-BlackTower dbus-daemon[1927]: [session uid=1000 pid=1927] Successfully activated service 'org.gnome.Terminal' Nov 2 17:51:20 chris-BlackTower systemd[1910]: Started GNOME Terminal Server. Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Nov 2 17:51:22 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:51:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:52:17 chris-BlackTower kernel: [ 5451.623104] usb 1-2: USB disconnect, device number 5 Nov 2 17:52:25 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545188] audit: type=1400 audit(1572717167.836:71): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/sbin/route" pid=15859 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545588] audit: type=1400 audit(1572717167.836:72): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15860 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545989] audit: type=1400 audit(1572717167.836:73): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15861 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.424278] usb 1-2: new high-speed USB device number 6 using ehci-pci Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584559] usb 1-2: New USB device found, idVendor=04b8, idProduct=1109, bcdDevice= 1.00 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584565] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584568] usb 1-2: Product: XP-960 Series Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584570] usb 1-2: Manufacturer: EPSON Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584573] usb 1-2: SerialNumber: 57355359303299 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.588547] usblp 1-2:1.1: usblp0: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1109 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.588832] usb-storage
[Touch-packages] [Bug 1851518] [NEW] [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Public bug reported: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RES.075.190529.SP dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950SBE-K01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9849A0Q-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No
[Touch-packages] [Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Only fails on arm64 now (all others good):
15-basic-resolver.c:58:46: error: ‘__NR_open’ undeclared (first use in this
function)
58 | if (seccomp_syscall_resolve_name("open") != __NR_open)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in libseccomp:
Fix Released
Status in libseccomp package in Ubuntu:
Triaged
Status in libseccomp source package in Eoan:
Triaged
Bug description:
Due to the python 3.8 transition in focal this was rebuilt but fails atm.
=>
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz
The simulations fail in this case:
batch name: 36-sim-ipc_syscalls
test mode: c
test type: bpf-sim
Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14
test mode: c
test type: bpf-valgrind
Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls
rc=14
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test mode: c
test type: bpf-valgrind
Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE
37-sim-ipc_syscalls_be rc=14
It is always the s390x test - even when running on i386/ppc64
On x86_64 this test succeeds:
Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
** Description changed: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. TODO: update after test rebuild - http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html - http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html + https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html + https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: Fix Committed Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: Fix Committed Status in python3.7 source package in Eoan: Fix Committed Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. TODO: update after test rebuild https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Offline build worked much better with these, but I still see some arches fail (see PPA) PPA: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1849785 -libseccomp-ftbfs/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) Status in libseccomp: Fix Released Status in libseccomp package in Ubuntu: Triaged Status in libseccomp source package in Eoan: Triaged Bug description: Due to the python 3.8 transition in focal this was rebuilt but fails atm. => https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz The simulations fail in this case: batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls rc=14 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE 37-sim-ipc_syscalls_be rc=14 It is always the s390x test - even when running on i386/ppc64 On x86_64 this test succeeds: Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 To manage notifications about this bug go to: https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug
# ls -l /usr/share/apport/symptoms/ubuntu-release-upgrader.py -rw-r--r-- 1 root root 214 May 17 16:32 /usr/share/apport/symptoms/ubuntu-release-upgrader.py # dpkg -S /usr/share/apport/symptoms/ubuntu-release-upgrader.py apport-symptoms: /usr/share/apport/symptoms/ubuntu-release-upgrader.py # debsums apport-symptoms /usr/share/apport/symptoms/_audio_checks.py OK /usr/share/apport/symptoms/_audio_data.py OK /usr/share/apport/symptoms/_audio_mixercontrol.py OK /usr/share/apport/symptoms/audio.py OK /usr/share/apport/symptoms/display.py OK /usr/share/apport/symptoms/security.pyOK /usr/share/apport/symptoms/storage.py OK /usr/share/apport/symptoms/ubuntu-release-upgrader.py OK /usr/share/doc/apport-symptoms/changelog.gz OK /usr/share/doc/apport-symptoms/copyright OK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850804 Title: Tab completion warnings with ubuntu-bug Status in apport package in Ubuntu: New Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Well the answer to the new fails is that we are now "too new" in my
tests I used kernel 5.3 and this is what Focal has. But the final fix
used 5.4-rc levels which brought in all the time64 things.
linux-libc-dev:amd64 5.3.0-21.22
5.3 already has the NR definitions like
/usr/include/x86_64-linux-gnu/bits/syscall.h:182:#ifdef __NR_clock_gettime64
But the updated seccomp code added things like:
src/arch-mips64-syscalls.c
626 +»··{ "clock_settime64", __PNR_clock_settime64 },
Usually there are compat defines inside seccomp include/seccomp.h
But the timers are not there.
So without the timers defined => tests fail re-resolving those
with them defined => build fails missing some other part of the definition.
What we overall need seems instead to be the slightly bigger set of:
44113f30 arch: add support for io-uring related system calls in kernel 5.1
0db8babb api: stop defining __NR_x values for syscalls that don't exist
80177ff2 build: ship seccomp-syscalls.h
be65b26b arch: update the internal syscall tables to Linux v5.4-rc4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in libseccomp:
Fix Released
Status in libseccomp package in Ubuntu:
Triaged
Status in libseccomp source package in Eoan:
Triaged
Bug description:
Due to the python 3.8 transition in focal this was rebuilt but fails atm.
=>
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz
The simulations fail in this case:
batch name: 36-sim-ipc_syscalls
test mode: c
test type: bpf-sim
Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14
test mode: c
test type: bpf-valgrind
Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls
rc=14
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
[Touch-packages] [Bug 1851504] Re: encrypted root fails to cryptsetup on disco
+source: https://git.launchpad.net/ubuntu/+source/cryptsetup/tree/debian/initramfs/hooks/cryptroot?id=applied/2%252.1.0-6#n414 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in cryptsetup: New Status in initramfs-tools package in Ubuntu: New Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+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 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked
Please, any new findings/new info? It is very annoying! :/ and got worse. I must go to TTY1 and `killall light-locker` in order to be able to use computer again... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1830408 Title: [nouveau][XFCE] Do not see login screen after screen is blanked Status in lightdm package in Ubuntu: New Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830408/+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 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked
PS: turning the computer off performs normally, there is no delay any more -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1830408 Title: [nouveau][XFCE] Do not see login screen after screen is blanked Status in lightdm package in Ubuntu: New Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830408/+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 1851504] Re: encrypted root fails to cryptsetup on disco
** Also affects: cryptsetup Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in cryptsetup: New Status in initramfs-tools package in Ubuntu: New Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+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 1851504] Re: encrypted root fails to cryptsetup on disco
WORKAROUND: Change line 429 to read: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done This changes the first regexp group from "(/lib.*)" to "(/.*)" allowing /usr/lib.* as well. After running update-initramfs -v -k 5.0.0-32-generic -c cryptsetup succeeds in mounting the encrypted root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in initramfs-tools package in Ubuntu: New Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1851504/+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 1851504] [NEW] encrypted root fails to cryptsetup on disco
Public bug reported: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; > do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco Status in initramfs-tools package in Ubuntu: New Bug description: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1851504/+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 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
I have tried quickly to just backport [1] but it still fails in a full cross arch PPA build OTOH adding those worked in the sbuild env when modifying things manually. There must be more to it. [1]: https://github.com/seccomp/libseccomp/commit/be65b26b67099be2b2b4890d736dbd1ad15adf36 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) Status in libseccomp: Fix Released Status in libseccomp package in Ubuntu: Triaged Status in libseccomp source package in Eoan: Triaged Bug description: Due to the python 3.8 transition in focal this was rebuilt but fails atm. => https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz The simulations fail in this case: batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls rc=14 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE 37-sim-ipc_syscalls_be rc=14 It is always the s390x test - even when running on i386/ppc64 On x86_64 this test succeeds: Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 To manage notifications about this bug go to:
[Touch-packages] [Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Oh it now became a real build issue (not on unit tests) by breaking very early
with things like:
arch-x86_64-syscalls.c:63:27: error: ‘__PNR_clock_getres_time64’ undeclared
here (not in a function)
63 | { "clock_getres_time64", __PNR_clock_getres_time64 },
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in libseccomp:
Fix Released
Status in libseccomp package in Ubuntu:
Triaged
Status in libseccomp source package in Eoan:
Triaged
Bug description:
Due to the python 3.8 transition in focal this was rebuilt but fails atm.
=>
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz
The simulations fail in this case:
batch name: 36-sim-ipc_syscalls
test mode: c
test type: bpf-sim
Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14
test mode: c
test type: bpf-valgrind
Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls
rc=14
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test mode: c
test type: bpf-valgrind
Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE
37-sim-ipc_syscalls_be rc=14
It is always the s390x test - even when running on i386/ppc64
On x86_64 this test succeeds:
Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions
--
Mailing
[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
Joe, thanks for reporting the bug. I am unable to reproduce the issue in my test env. Can you please provide a step-by-step procedure to reproduce it on a clean 18.04 installation? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/375205 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) Status in libseccomp: Fix Released Status in libseccomp package in Ubuntu: Triaged Status in libseccomp source package in Eoan: Triaged Bug description: Due to the python 3.8 transition in focal this was rebuilt but fails atm. => https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz The simulations fail in this case: batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls rc=14 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE 37-sim-ipc_syscalls_be rc=14 It is always the s390x test - even when running on i386/ppc64 On x86_64 this test succeeds: Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 To manage notifications about this bug go to: https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
Unsure the system has enough information from the hardware to tell appart a disconnect from a power off, there is no mechanical check that something is plugged in the port, it's just depending on whether a signal is received. That said it looks like a duplicate of #1847570 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1850804] Re: Tab completion warnings with ubuntu-bug
What about -ls -l /usr/share/apport/symptoms/ubuntu-release-upgrader.py -dpkg -S /usr/share/apport/symptoms/ubuntu-release-upgrader.py -debsums apport-symptoms The file should be there... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850804 Title: Tab completion warnings with ubuntu-bug Status in apport package in Ubuntu: New Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850804/+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 1537056] Re: apt-add-repository returns "user or team does not exist." when erroring out due to proxy auth needed
** Summary changed:
- apt-add-repository always returns "user or team does not exist." for ppa repos
+ apt-add-repository returns "user or team does not exist." when erroring out
due to proxy auth needed
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1537056
Title:
apt-add-repository returns "user or team does not exist." when
erroring out due to proxy auth needed
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
I have just installed a fresh Ubuntu 15.10 to my machine and run into
trouble with adding ppa repositories using apt-add-repository:
for e.g. running
apt-add-repository ppa:git-core/ppa
Cannot add PPA: 'ppa:~git-core/ubuntu/ppa'.
ERROR: '~git-core' user or team does not exist.
After debugging a lot of code, I found the trouble, the used proxy-
server needs authentification but the apt-add-repository does not
throw a correct error message fro this case:
The PPAException raised here seems to be interpreted as not available,
which is rather hard to debug.
def _get_https_content_py3(lp_url):
print("RETRIEVING URL: %s"%lp_url)
try:
request = urllib.request.Request(str(lp_url), headers={"Accept":"
application/json"})
lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
json_data = lp_page.read().decode("utf-8", "strict")
print("RV: %s"%str(json_data))
except (URLError, HTTPException) as e:
# HTTPException doesn't have a reason but might have a string
# representation
print(e)
reason = hasattr(e, "reason") and e.reason or e
raise PPAException("Error reading %s: %s" % (lp_url, reason), e)
The last print(e) gives me the hint what went wrong:
For the future it would be great to get a correct error message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1537056/+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 1851451] Re: Performance is not good system freeze a lot of time
seems a disk issue rather than an xorg bug ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1851451 Title: Performance is not good system freeze a lot of time Status in xorg package in Ubuntu: Invalid Bug description: freeze mouse and keyboard ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 20:46:07 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] InstallationDate: Installed on 2019-11-04 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 064e:c346 Suyin Corp. HP TrueVision HD Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.36 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1AP08EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851451/+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 1850762] Re: stub-resolver no longer optional, systemd dns broken
Dimitri, indeed, my bad. In other news: it seems that this issue has been known for a while and somebody has been (trying to) solv(e|ing) it - I guess the solution will come to Ubuntu at some stage... https://github.com/systemd/systemd/pull/12004 Thanks for the feedback, looking forward to a working version in the future (not looking forward to increasingly complex interdependencies, but hey, who am I to complain, I could always start my own distribution without systemd, I know...) -- 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/1850762 Title: stub-resolver no longer optional, systemd dns broken Status in systemd package in Ubuntu: Incomplete Bug description: systemd name resolution is broken in professional setups. https://askubuntu.com/a/974482 used to provide a solution, simply ignore stub-resolution (which is broken) and fall back to the normal name resolution as configured (e.g. through dhcp). this solution does not seem to be available after upgrading to ubuntu 19.10 - there is no clean resolv.conf left. please advise as to how systemd name resolution through its local service can be disabled now (as it is broken). Thanks $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I expected my computer to resolve names (it used to do so after the workaround for the systemd bug) It does not resolve all names anymore (and the old workaround doesn't work anymore). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: MATE Date: Thu Oct 31 10:02:05 2019 InstallationDate: Installed on 2019-04-10 (203 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) MachineType: LENOVO 20L8S29W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=fddb227e-dc5d-4f78-b605-443eeb5bf5c9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to eoan on 2019-10-24 (6 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S29W00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L8S29W00:pvrThinkPadT480s:rvnLENOVO:rn20L8S29W00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S29W00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1850762/+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 1843757] Re: protobuf ftbfs in eoan (ppc64el)
Ignore the above about 3.10. I tried to compile without optimization. That's why I didn't notice the problem. So 3.10 is also affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1843757 Title: protobuf ftbfs in eoan (ppc64el) Status in protobuf package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441264543/buildlog_ubuntu-eoan- ppc64el.protobuf_3.6.1.3-2_BUILDING.txt.gz g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DHAVE_PTHREAD=1 -DHAVE_ZLIB=1 -Wall -Wextra -Werror -Wno-unused-parameter -g -O3 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o google/protobuf/no_warning_test-any_test.pb.o `test -f 'google/protobuf/any_test.pb.cc' || echo './'`google/protobuf/any_test.pb.cc In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/any_test.pb.h:9, from google/protobuf/any_test.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestAny::SharedCtor()’ at google/protobuf/any_test.pb.cc:163:11, inlined from ‘protobuf_unittest::TestAny::TestAny()’ at google/protobuf/any_test.pb.cc:145:13, inlined from ‘void protobuf_google_2fprotobuf_2fany_5ftest_2eproto::InitDefaultsTestAny()’ at google/protobuf/any_test.pb.cc:141:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [49, 52] from the object at ‘protobuf_unittest::_TestAny_default_instance_’ is out of the bounds of referenced subobject ‘protobuf_unittest::TestAny::any_value_’ with type ‘google::protobuf::Any*’ at offset 40 [-Werror=array-bounds] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest)); | ~~~^~ cc1plus: all warnings being treated as errors make[4]: *** [Makefile:4468: google/protobuf/no_warning_test-any_test.pb.o] Error 1 make[4]: *** Waiting for unfinished jobs In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/unittest_lite.pb.h:9, from google/protobuf/unittest_lite.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestAllTypesLite_NestedMessage::SharedCtor()’ at google/protobuf/unittest_lite.pb.cc:792:11, inlined from ‘protobuf_unittest::TestAllTypesLite_NestedMessage::TestAllTypesLite_NestedMessage()’ at google/protobuf/unittest_lite.pb.cc:777:13, inlined from ‘void protobuf_google_2fprotobuf_2funittest_5flite_2eproto::InitDefaultsTestAllTypesLite_NestedMessage()’ at google/protobuf/unittest_lite.pb.cc:773:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [33, 36] from the object at ‘protobuf_unittest::_TestAllTypesLite_NestedMessage_default_instance_’ is out of the bounds of referenced subobject ‘protobuf_unittest::TestAllTypesLite_NestedMessage::cc_’ with type ‘long int’ at offset 24 [-Werror=array-bounds] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest)); | ~~~^~ cc1plus: all warnings being treated as errors make[4]: *** [Makefile:4412: google/protobuf/no_warning_test-unittest_lite.pb.o] Error 1 In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/map_lite_unittest.pb.h:9, from google/protobuf/map_lite_unittest.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestRequiredLite::SharedCtor()’ at google/protobuf/map_lite_unittest.pb.cc:6417:11, inlined from ‘protobuf_unittest::TestRequiredLite::TestRequiredLite()’ at google/protobuf/map_lite_unittest.pb.cc:6394:13, inlined from ‘void protobuf_google_2fprotobuf_2fmap_5flite_5funittest_2eproto::InitDefaultsTestRequiredLite()’ at google/protobuf/map_lite_unittest.pb.cc:6390:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [29, 36] from the object at ‘protobuf_unittest::_TestRequiredLite_default_instance_’ is out of the bounds of referenced subobject ‘protobuf_unittest::TestRequiredLite::a_’ with type ‘int’ at offset 24
[Touch-packages] [Bug 1843757] Re: protobuf ftbfs in eoan (ppc64el)
I have the same protobuf problem with my personal code. Generated by protobuf code is definitely not compatible with currently installed system headers. I also tested protobuf-3.10 and it works fine. So I think the protobuf package has to be upgraded in the Ubuntu repo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1843757 Title: protobuf ftbfs in eoan (ppc64el) Status in protobuf package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441264543/buildlog_ubuntu-eoan- ppc64el.protobuf_3.6.1.3-2_BUILDING.txt.gz g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DHAVE_PTHREAD=1 -DHAVE_ZLIB=1 -Wall -Wextra -Werror -Wno-unused-parameter -g -O3 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o google/protobuf/no_warning_test-any_test.pb.o `test -f 'google/protobuf/any_test.pb.cc' || echo './'`google/protobuf/any_test.pb.cc In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/any_test.pb.h:9, from google/protobuf/any_test.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestAny::SharedCtor()’ at google/protobuf/any_test.pb.cc:163:11, inlined from ‘protobuf_unittest::TestAny::TestAny()’ at google/protobuf/any_test.pb.cc:145:13, inlined from ‘void protobuf_google_2fprotobuf_2fany_5ftest_2eproto::InitDefaultsTestAny()’ at google/protobuf/any_test.pb.cc:141:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [49, 52] from the object at ‘protobuf_unittest::_TestAny_default_instance_’ is out of the bounds of referenced subobject ‘protobuf_unittest::TestAny::any_value_’ with type ‘google::protobuf::Any*’ at offset 40 [-Werror=array-bounds] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest)); | ~~~^~ cc1plus: all warnings being treated as errors make[4]: *** [Makefile:4468: google/protobuf/no_warning_test-any_test.pb.o] Error 1 make[4]: *** Waiting for unfinished jobs In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/unittest_lite.pb.h:9, from google/protobuf/unittest_lite.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestAllTypesLite_NestedMessage::SharedCtor()’ at google/protobuf/unittest_lite.pb.cc:792:11, inlined from ‘protobuf_unittest::TestAllTypesLite_NestedMessage::TestAllTypesLite_NestedMessage()’ at google/protobuf/unittest_lite.pb.cc:777:13, inlined from ‘void protobuf_google_2fprotobuf_2funittest_5flite_2eproto::InitDefaultsTestAllTypesLite_NestedMessage()’ at google/protobuf/unittest_lite.pb.cc:773:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [33, 36] from the object at ‘protobuf_unittest::_TestAllTypesLite_NestedMessage_default_instance_’ is out of the bounds of referenced subobject ‘protobuf_unittest::TestAllTypesLite_NestedMessage::cc_’ with type ‘long int’ at offset 24 [-Werror=array-bounds] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest)); | ~~~^~ cc1plus: all warnings being treated as errors make[4]: *** [Makefile:4412: google/protobuf/no_warning_test-unittest_lite.pb.o] Error 1 In file included from /usr/include/string.h:494, from ./google/protobuf/stubs/port.h:38, from ./google/protobuf/stubs/common.h:46, from ./google/protobuf/map_lite_unittest.pb.h:9, from google/protobuf/map_lite_unittest.pb.cc:4: In function ‘void* memset(void*, int, size_t)’, inlined from ‘void protobuf_unittest::TestRequiredLite::SharedCtor()’ at google/protobuf/map_lite_unittest.pb.cc:6417:11, inlined from ‘protobuf_unittest::TestRequiredLite::TestRequiredLite()’ at google/protobuf/map_lite_unittest.pb.cc:6394:13, inlined from ‘void protobuf_google_2fprotobuf_2fmap_5flite_5funittest_2eproto::InitDefaultsTestRequiredLite()’ at google/protobuf/map_lite_unittest.pb.cc:6390:1: /usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:71:33: error: ‘void* __builtin_memset(void*, int, long unsigned int)’ offset [29, 36] from the object at
[Touch-packages] [Bug 1851453] Re: mir FTBFS in focal, blocks nettle transition
** Changed in: mir (Ubuntu) Assignee: (unassigned) => Chris Halse Rogers (raof) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1851453 Title: mir FTBFS in focal, blocks nettle transition Status in mir package in Ubuntu: New Bug description: a no-change rebuild of mir in focal has failed, for reasons that appear unrelated to nettle itself. [...] [ 61%] Linking CXX shared module ../../lib/client-modules/dummy.so cd /<>/build-amd64/tests/mir_test_framework && /usr/bin/cmake -E cmake_link_script CMakeFiles/mirclientplatformstub.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -Werror -Wno-psabi -ffat-lto-objects -Wno-error=null-dereference -Wno-error=overloaded-virtual -Wno-sign-compare -fno-lto -Dregister= -Wl,--version-script,/<>/tests/mir_test_framework/symbols-client.map -Wl,-Bsymbolic-fu nctions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -fuse-ld=gold -Wl,--no-undefined -shared -o ../../lib/client-modules/dummy.so CMakeFiles/mirclientplatformstub.dir/stub_client_platform_module.cpp.o -Wl,-rpath,/<>/build-amd64/lib: libmir-test-framework-static.a -lumockdev -lgobject-2.0 -lglib-2.0 -lumockdev -lgobject-2.0 -lglib-2.0 ../../lib/libmirserver.so.50 ../../lib/libmirplatform.so.16 ../../lib/libmirwayland.so.0 -lwayland-server ../../src/platforms/common/server/libserver_platform_common.a ../../src/platforms/common/server/kms-utils/libkms_utils.a -ldrm -ldrm /usr/lib/x86_64-linux-gnu/libEGL.so -lGLESv2 -lGLESv2 -lepoxy -lepoxy -ludev -ludev -lgio-2.0 -lgio-2.0 -luuid -luuid -lxcb -lxcb -lxcb-composite -lxcb-composite -lxcb-xfixes -lxcb-xfixes -lxcb-render -lxcb-render -lXcursor -lXcursor -llttng-ust -ldl -llttng-ust -latomic ../../lib/libmirclient.so.9 ../../lib/libmircommon.so.7 ../../src/capnproto/libmircapnproto.a /usr/lib/x86_64-linux-gnu/libcapnp-0.7.0.so /usr/lib/x86_64-linux-gnu/libkj-0.7.0.so -lpthread -pthread ../../lib/libmircore.so.1 -ldl ../../lib/libmirprotobuf.so.3 /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so ../../lib/libmircookie.so.2 -lnettle /usr/lib/x86_64-linux-gnu/libxkbcommon.so /usr/lib/x86_64-linux-gnu/libboost_date_time.so /usr/lib/x86_64-linux-gnu/libboost_system.so /usr/lib/x86_64-linux-gnu/libboost_program_options.so /usr/lib/x86_64-linux-gnu/libboost_filesystem.so /usr/lib/x86_64-linux-gnu/libboost_iostreams.so /usr/lib/x86_64-linux-gnu/libboost_regex.so /usr/lib/x86_64-linux-gnu/libgtest.a /usr/lib/x86_64-linux-gnu/libgtest_main.a /usr/lib/x86_64-linux-gnu/libgtest.a /usr/lib/x86_64-linux-gnu/libgtest_main.a ../../libGMock.a -lpthread -lgobject-2.0 -lglib-2.0 -lumockdev -lgobject-2.0 -lglib-2.0 /usr/src/gmock/src/gmock.cc:135: error: undefined reference to 'testing::Message::Message()' /usr/src/gmock/src/gmock.cc:135: error: undefined reference to 'testing::internal::ParseInt32(testing::Message const&, char const*, int*)' /usr/src/gmock/src/gmock-internal-utils.cc:181: error: undefined reference to 'testing::UnitTest::GetInstance()' /usr/src/gmock/src/gmock-internal-utils.cc:181: error: undefined reference to 'testing::internal::GetCurrentOsStackTraceExceptTop[abi:cxx11](testing::UnitTest*, int)' /usr/include/gtest/internal/gtest-port.h:1651: error: undefined reference to 'testing::internal::GTestLog::GTestLog(testing::internal::GTestLogSeverity, char const*, int)' /usr/include/gtest/internal/gtest-port.h:1651: error: undefined reference to 'testing::internal::GTestLog::~GTestLog()' [...] (https://launchpad.net/ubuntu/+source/mir/1.4.0-0ubuntu4/+build/18005823) This is holding up a mass of intertwined start-of-cycle library transitions in focal-proposed right now. Please fix this asap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1851453/+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 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Code is on https://github.com/seccomp/libseccomp/tree/release-2.4 now. But an official release would need 2.4.2 to be tagged by upstream. But now fixes can be cherry-picked to fix the FTBFS in E+F ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) Status in libseccomp: Fix Released Status in libseccomp package in Ubuntu: Triaged Status in libseccomp source package in Eoan: Triaged Bug description: Due to the python 3.8 transition in focal this was rebuilt but fails atm. => https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz The simulations fail in this case: batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: FAILURE 36-sim-ipc_syscalls rc=14 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind Test 37-sim-ipc_syscalls_be%%013-1 result: FAILURE 37-sim-ipc_syscalls_be rc=14 It is always the s390x test - even when running on i386/ppc64 On x86_64 this test succeeds: Test 36-sim-ipc_syscalls%%025-1 result: SUCCESS batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 To manage notifications about this bug go to: https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions -- Mailing list:
