[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
** Description changed: + [Impact] + + * Just as of yesterday we have a new libseccomp in all releases. +This brings some new code and features which might impact packages. +For qemu being one of the few that is not so much a problem in many +cases. Prior to Disco we didn't have code in qemu using the new +libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being +release level) will be installed. +But in Disco people might have installed and not updated libseccomp +but install/upgrade to a qemu that was built against that new +libseccomp. Due to that qemu will get a runtime dependency that is +not picked up automatically - this would break all qemu execution +being blocked by a failure to install seccomp filters. + + * To fix that we will add an explicit versioned dependency to qemu to +make sure the rebuild will ensure that the right library version is +available. + + * This is needed for qemu-system* which all depend on qemu-system- +common so to avoid too much noise changing all qemu-system* packages +the dependency it added there. + + + [Test Case] + + * ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1) +is also installed (not staying on 2.3) + + * Then install qemu and run +$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny + +which should not trigger this (when fixed) + error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel + + + [Regression Potential] + + * Well, the regressions might be triggered by pushing the new +libseccomp, not by this dependency fixup. The security Team has +checked and this seems to be the only affected code in the archive. +So libseccomp was pushed to fix CVEs. I have thought if it is a +regression that users of qemu will now be forced to use the newer +libseccomp, but since it would be unusable without that is no +important argument. And it is strongly recommended to upgrade for +security reasons as well. + + [Other Info] + + * n/a + + --- + It started with some of my usual KVM checks and found them failing on Disco with: error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel I realized it works on X/B/C/E but not in a D container It worked ~4 weeks ago. This test can be simplified to one command: $ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny With strace I found different behavior: Good: [pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11> [pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.44> [pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251> Bad: [pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17> [pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.14> [pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> The difference seems to come from being built against seccomp as in Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad). The dependency on the built package stayed libseccomp2 (>= 2.3.0) It did not pick up 2.4 via e.g. shlibs. If I install libseccomp2 2.4 from -proposed the issue is gone. Strace now looks like: [pid 1788] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.15> [pid 1788] 0.004167 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.13> [pid 1788] 0.98 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> [pid 1788] 0.54 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.22> [pid 1788] 0.61 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.17> [pid 1788] 0.001477 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x564de3852560}) = 0 <0.000288> This is in all releases proposed to fix CVE-2019-9893 I was just ?lucky? to pick it up with my qemu build in the PPA that has propose
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
Thanks Jamie, as discussed an explicit dependency as fix will be part of the next SRU upload to qemu to avoid anybody running into trouble due to this. -- 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/1830859 Title: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4 Status in libseccomp package in Ubuntu: Won't Fix Status in qemu package in Ubuntu: Triaged Bug description: It started with some of my usual KVM checks and found them failing on Disco with: error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel I realized it works on X/B/C/E but not in a D container It worked ~4 weeks ago. This test can be simplified to one command: $ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny With strace I found different behavior: Good: [pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11> [pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.44> [pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251> Bad: [pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17> [pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.14> [pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> The difference seems to come from being built against seccomp as in Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad). The dependency on the built package stayed libseccomp2 (>= 2.3.0) It did not pick up 2.4 via e.g. shlibs. If I install libseccomp2 2.4 from -proposed the issue is gone. Strace now looks like: [pid 1788] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.15> [pid 1788] 0.004167 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.13> [pid 1788] 0.98 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> [pid 1788] 0.54 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.22> [pid 1788] 0.61 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.17> [pid 1788] 0.001477 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x564de3852560}) = 0 <0.000288> This is in all releases proposed to fix CVE-2019-9893 I was just ?lucky? to pick it up with my qemu build in the PPA that has proposed enabled. Now there might be some toolchain detail to this as well. As I built qemu for B/C as well and they built against the proposed 2.4 versions as well. But in B/C things work with new qemu builds and old libseccomp2 installed. Eoan on the other hand works by having libseccomp2 2.4.1-0ubuntu0.19.10.3 already migrated. But that "luck" of B/C working might be specific to Qemus code, other rebuilds against the new libseccomp2 might fail as well in B/C and further. Shlibs detection is based on these symbols but my new qemu build is not calling these so it dependency stays at 2.3. Until a simpler testcase is found, I have set up two new PPAs: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830859-with-proposed-seccomp https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830859-without-proposed-seccomp In comment #5 I debugged the case and found the new "dependency" As a summary: - the libseccomp-dev 2.4 headers being installed at build time - code can detect now the availability of SCMP_ACT_KILL_PROCESS - code might decide to use SCMP_ACT_KILL_PROCESS - if code runs without libseccomp2 2.4 installed it breaks ### some related Build logs ### Cosmic rebuild against 2.4, not affected by the issue https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3729/+build/16858331/+files/buildlog_ubuntu-cosmic-amd64.qemu_1%3A2.12+dfsg-3ubuntu8.9~ppa1_BUILDING.txt.gz Disco rebuild against 2.4, affected by the issue https://launchpadlibrarian.net/425689546/buildlog_ubuntu-disco-amd64.qemu_1%3A3.1+dfsg-2ubuntu3.2~ppa1_BUILDING.txt.gz Disco build against 2.3 (working) https://launchpadlibrarian.net/422884897/buildlog_ubuntu-disco-amd64.qemu_1%3A3.1+dfsg-2ubuntu3.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs
[Touch-packages] [Bug 1759172] Re: python 2.7 test_ssl hits AttributeError with openssl 1.1.1
** Changed in: python Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1759172 Title: python 2.7 test_ssl hits AttributeError with openssl 1.1.1 Status in Python: Confirmed Status in python2.7 package in Ubuntu: New Bug description: autopkgtest fails with openssl1.1.1 As seen at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/p/python2.7/20180927_033108_115d8@/log.gz == ERROR: test_tls1_3 (test.test_ssl.ThreadedTests) -- Traceback (most recent call last): File "/usr/lib/python2.7/test/test_ssl.py", line 2815, in test_tls1_3 with context.wrap_socket(socket.socket()) as s: AttributeError: __exit__ To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1759172/+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 1829077] Re: disco 19.04 doesn't shutdown
Does this happen to older Ubuntu releases? -- 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/1829077 Title: disco 19.04 doesn't shutdown Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1831162] Re: Xorg freeze
Unfortunately we have to declare this bug invalid. The Nvidia driver version 430 is not yet part of Ubuntu so we can't handle its bugs in Launchpad here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1831162 Title: Xorg freeze Status in Ubuntu: Invalid Bug description: Nvidia driver 430 is definitely the cause of freezing. I have reinstalled ubunutu twice! I also use an EGPU with my system, the 1080 ti. I have an nvidia dgpu, the 1050 ti. My computer is the dell xps 15 9570. I have finally achieved a stable system state with the nvidia 418.67 driver. So what I did was installed the lasted release of cuda 10.1 via the local run file method. That method allows you to install the 418.67 driver and cuda 10.1 all in a nice package. I also have nouveau.modeset=0 in grub set to run on every boot. I also uncommented the wayfarenabled=false. I also use gswitcher, a small program designed to make the xorg conf file for the egpu. I have disabled secure boot and cstates Good luck fixing nvidia driver 430. Thank you for your dedication! Peter 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.67 Sat Apr 6 03:07:24 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10) ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 30 19:53:15 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-05-30 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=24f351e3-258b-46a3-8a35-bf4806a89b1c ro quiet splash nouveau.modeset=0 nvidia-drm.modeset=0 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/+bug/1831162/+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 1831074] Re: In high fidelity playback, front right side of headset doesn't work
** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Summary changed: - In high fidelity playback, front right side of headset doesn't work + [JBL tune 160BT] In high fidelity playback, front right side of headset doesn't work -- 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/1831074 Title: [JBL tune 160BT] In high fidelity playback, front right side of headset doesn't work Status in pulseaudio package in Ubuntu: New Bug description: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831074/+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 1831162] [NEW] Xorg freeze
Public bug reported: Nvidia driver 430 is definitely the cause of freezing. I have reinstalled ubunutu twice! I also use an EGPU with my system, the 1080 ti. I have an nvidia dgpu, the 1050 ti. My computer is the dell xps 15 9570. I have finally achieved a stable system state with the nvidia 418.67 driver. So what I did was installed the lasted release of cuda 10.1 via the local run file method. That method allows you to install the 418.67 driver and cuda 10.1 all in a nice package. I also have nouveau.modeset=0 in grub set to run on every boot. I also uncommented the wayfarenabled=false. I also use gswitcher, a small program designed to make the xorg conf file for the egpu. I have disabled secure boot and cstates Good luck fixing nvidia driver 430. Thank you for your dedication! Peter 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.67 Sat Apr 6 03:07:24 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10) ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 30 19:53:15 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-05-30 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=24f351e3-258b-46a3-8a35-bf4806a89b1c ro quiet splash nouveau.modeset=0 nvidia-drm.modeset=0 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze possible-manual-nvidia-install ubuntu -- 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/1831162 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Nvidia driver 430 is definitely the cause of freezing. I have reinstalled ubunutu twice! I also use an EGPU with my system, the 1080 ti. I have an nvidia dgpu, the 1050 ti. My computer is the dell xps 15 9570. I have finally achieved a stable system state with the nvidia 418.67 driver. So what I did was installed the lasted release of cuda 10.1 via the local run file method. That method allows you to install the 418.67 driver and cuda 10.1 all in a nice package. I also have nouveau.modeset=0 in grub set to run on every boot. I also uncommented the wayfarenabled=false. I also use gswitcher, a small program designed to make the xo
[Touch-packages] [Bug 1830479] Re: testcases expect first kernel log line, but not always in logs
** Changed in: systemd (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1830479 Title: testcases expect first kernel log line, but not always in logs Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Won't Fix Status in systemd package in Debian: New Bug description: [impact] boot-and-services and cmdline-upstart-boot expect the first(ish) kernel log line to be in the system logs, but that is not guaranteed to be in the logs. [test case] run autopkgtest on arm64 with the current kernel, whose kernel log size is too small for journald or rsyslogd to capture the first kernel log messages. [regression potential] low; testcase fix only. [other info] the specific cause of this currently is too-small kernel log buffer size on arm64, which is being fixed in bug 1824864, but increasing amounts of boot time logging may cause a failure again, or custom kernel configs with small log buffers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830479/+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 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
FYI, libseccomp is now published: https://usn.ubuntu.com/4001-1/ -- 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/1830859 Title: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4 Status in libseccomp package in Ubuntu: Won't Fix Status in qemu package in Ubuntu: Triaged Bug description: It started with some of my usual KVM checks and found them failing on Disco with: error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel I realized it works on X/B/C/E but not in a D container It worked ~4 weeks ago. This test can be simplified to one command: $ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny With strace I found different behavior: Good: [pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11> [pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.44> [pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251> Bad: [pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17> [pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.14> [pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> The difference seems to come from being built against seccomp as in Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad). The dependency on the built package stayed libseccomp2 (>= 2.3.0) It did not pick up 2.4 via e.g. shlibs. If I install libseccomp2 2.4 from -proposed the issue is gone. Strace now looks like: [pid 1788] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.15> [pid 1788] 0.004167 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.13> [pid 1788] 0.98 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1 EINVAL (Invalid argument) <0.13> [pid 1788] 0.54 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.22> [pid 1788] 0.61 seccomp(SECCOMP_GET_ACTION_AVAIL, 0, [SECCOMP_RET_KILL_PROCESS]) = 0 <0.17> [pid 1788] 0.001477 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x564de3852560}) = 0 <0.000288> This is in all releases proposed to fix CVE-2019-9893 I was just ?lucky? to pick it up with my qemu build in the PPA that has proposed enabled. Now there might be some toolchain detail to this as well. As I built qemu for B/C as well and they built against the proposed 2.4 versions as well. But in B/C things work with new qemu builds and old libseccomp2 installed. Eoan on the other hand works by having libseccomp2 2.4.1-0ubuntu0.19.10.3 already migrated. But that "luck" of B/C working might be specific to Qemus code, other rebuilds against the new libseccomp2 might fail as well in B/C and further. Shlibs detection is based on these symbols but my new qemu build is not calling these so it dependency stays at 2.3. Until a simpler testcase is found, I have set up two new PPAs: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830859-with-proposed-seccomp https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830859-without-proposed-seccomp In comment #5 I debugged the case and found the new "dependency" As a summary: - the libseccomp-dev 2.4 headers being installed at build time - code can detect now the availability of SCMP_ACT_KILL_PROCESS - code might decide to use SCMP_ACT_KILL_PROCESS - if code runs without libseccomp2 2.4 installed it breaks ### some related Build logs ### Cosmic rebuild against 2.4, not affected by the issue https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3729/+build/16858331/+files/buildlog_ubuntu-cosmic-amd64.qemu_1%3A2.12+dfsg-3ubuntu8.9~ppa1_BUILDING.txt.gz Disco rebuild against 2.4, affected by the issue https://launchpadlibrarian.net/425689546/buildlog_ubuntu-disco-amd64.qemu_1%3A3.1+dfsg-2ubuntu3.2~ppa1_BUILDING.txt.gz Disco build against 2.3 (working) https://launchpadlibrarian.net/422884897/buildlog_ubuntu-disco-amd64.qemu_1%3A3.1+dfsg-2ubuntu3.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1830859/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1814980] Re: timedatectl set-timezone UTC Fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1814980 Title: timedatectl set-timezone UTC Fails Status in systemd package in Ubuntu: Confirmed Bug description: Sorry for the pre-mature post. First time using this interface. I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ``` Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` If there's anything else that you need, let me know!. EDIT: ``` ubuntu@ip-172-31-26-66:~$ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` (hostname is different because this is a new instance, same AMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+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 1831156] [NEW] samsung clp-680nd does not print duplex
Public bug reported: My Samsung CLP-680ND printer is set up on a wired network. It works correctly from a Windows 10 laptop, printing duplex (double sided) pages. On Ubuntu 18.04 and 18.10 it does not print duplex although the option can be selected on the print dialogue. Otherwise printing is OK. It used to work but I don't know which upgrade broke it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.3 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 CurrentDesktop: ubuntu:GNOME Date: Thu May 30 22:47:02 2019 Lpstat: device for CLP-680: dnssd://Samsung%20CLP-680%20Series%20(SEC84251901BD4B)._ipp._tcp.local/?uuid=16a65700-007c-1000-bb49-84251901bd4b device for QL-500: usb://Brother/QL-500?serial=K9G909359 device for Samsung_CLP_680_Series_SEC84251901BD4B_: ipp://SEC84251901BD4B.local:631/ipp/printer MachineType: Dell Inc. OptiPlex 990 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/QL-500.ppd', '/etc/cups/ppd/Samsung_CLP_680_Series_SEC84251901BD4B_.ppd', '/etc/cups/ppd/CLP-680.ppd'] failed with exit code 2: grep: /etc/cups/ppd/QL-500.ppd: Permission denied grep: /etc/cups/ppd/Samsung_CLP_680_Series_SEC84251901BD4B_.ppd: Permission denied grep: /etc/cups/ppd/CLP-680.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=aa06cf80-1d26-4a3d-942b-452087493fe9 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2019-05-30 (0 days ago) dmi.bios.date: 07/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0VNP2H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/25/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug cosmic third-party-packages -- 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/1831156 Title: samsung clp-680nd does not print duplex Status in cups package in Ubuntu: New Bug description: My Samsung CLP-680ND printer is set up on a wired network. It works correctly from a Windows 10 laptop, printing duplex (double sided) pages. On Ubuntu 18.04 and 18.10 it does not print duplex although the option can be selected on the print dialogue. Otherwise printing is OK. It used to work but I don't know which upgrade broke it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.3 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 CurrentDesktop: ubuntu:GNOME Date: Thu May 30 22:47:02 2019 Lpstat: device for CLP-680: dnssd://Samsung%20CLP-680%20Series%20(SEC84251901BD4B)._ipp._tcp.local/?uuid=16a65700-007c-1000-bb49-84251901bd4b device for QL-500: usb://Brother/QL-500?serial=K9G909359 device for Samsung_CLP_680_Series_SEC84251901BD4B_: ipp://SEC84251901BD4B.local:631/ipp/printer MachineType: Dell Inc. OptiPlex 990 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/QL-500.ppd', '/etc/cups/ppd/Samsung_CLP_680_Series_SEC84251901BD4B_.ppd', '/etc/cups/ppd/CLP-680.ppd'] failed with exit code 2: grep: /etc/cups/ppd/QL-500.ppd: Permission denied grep: /etc/cups/ppd/Samsung_CLP_680_Series_SEC84251901BD4B_.ppd: Permission denied grep: /etc/cups/ppd/CLP-680.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=aa06cf80-1d26-4a3d-942b-452087493fe9 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2019-05-30 (0 days ago) dmi.bios.date: 07/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0VNP2H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/25/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https:/
[Touch-packages] [Bug 1831150] Re: security.capability extended attributes not restored upon extraction
** Bug watch added: GNU Savannah Bug Tracker #56421 http://savannah.gnu.org/bugs/?56421 ** Also affects: tar via http://savannah.gnu.org/bugs/?56421 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1831150 Title: security.capability extended attributes not restored upon extraction Status in GNU tar: Unknown Status in tar package in Ubuntu: New Status in tar package in Debian: Unknown Bug description: The tar info page and upstream documentation indicate that when --xattr is used "all names are stored in the archive (or extracted, if using '--extract')", however when using --xattr with extract the security.capability extended attributes are not restored. If one also uses "--xattrs-include=*" then the security.capability extended attributes will be restored. [Test Case] mkdir orig restore touch orig/file_with_capability_and_user_xattr setcap cap_net_raw=p orig/file_with_capability_and_user_xattr (eoan-amd64)root@impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr # file: orig/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" I think tar's extract behavior should be changed to match that of create so that all names are actually extracted. To manage notifications about this bug go to: https://bugs.launchpad.net/tar/+bug/1831150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
Lol On Thu, 30 May 2019, 20:20 Rafael David Tinoco, < rafaeldtin...@kernelpath.com> wrote: > xnox, it looks like you're missing a "$" in md5sum command from: > > > https://launchpadlibrarian.net/426017250/systemd_240-6ubuntu7_240-6ubuntu8.diff.gz > > for the -proposed systemd version: > > /sbin/dhclient-script: 57: /etc/dhcp/dhclient-enter-hooks.d/resolved: > Syntax error: "(" unexpected > > Adding it solved my boot problem (systemd stucks in networking > services). > > cheers o/ > > -- > You received this bug notification because you are subscribed to systemd > in Ubuntu. > Matching subscriptions: systemd > https://bugs.launchpad.net/bugs/1805183 > > Title: > systemd-resolved constantly restarts on Bionic upgraded from Xenial > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Confirmed Status in systemd source package in Disco: Confirmed Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1831150] [NEW] security.capability extended attributes not restored upon extraction
Public bug reported: The tar info page and upstream documentation indicate that when --xattr is used "all names are stored in the archive (or extracted, if using '-- extract')", however when using --xattr with extract the security.capability extended attributes are not restored. If one also uses "--xattrs-include=*" then the security.capability extended attributes will be restored. [Test Case] mkdir orig restore touch orig/file_with_capability_and_user_xattr setcap cap_net_raw=p orig/file_with_capability_and_user_xattr (eoan-amd64)root@impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr # file: orig/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" I think tar's extract behavior should be changed to match that of create so that all names are actually extracted. ** Affects: tar (Ubuntu) Importance: Undecided Status: New ** Affects: tar (Debian) Importance: Unknown Status: Unknown ** Tags: eoan ** Bug watch added: Debian Bug tracker #927261 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927261 ** Also affects: tar (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927261 Importance: Unknown Status: Unknown ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1831150 Title: security.capability extended attributes not restored upon extraction Status in tar package in Ubuntu: New Status in tar package in Debian: Unknown Bug description: The tar info page and upstream documentation indicate that when --xattr is used "all names are stored in the archive (or extracted, if using '--extract')", however when using --xattr with extract the security.capability extended attributes are not restored. If one also uses "--xattrs-include=*" then the security.capability extended attributes will be restored. [Test Case] mkdir orig restore touch orig/file_with_capability_and_user_xattr setcap cap_net_raw=p orig/file_with_capability_and_user_xattr (eoan-amd64)root@impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr # file: orig/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" I think tar's extract behavior should be changed to match that of create so that all names are actually extracted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1831150/+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 1810241] Re: NULL dereference when decompressing specially crafted archives
** Changed in: tar (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1810241 Title: NULL dereference when decompressing specially crafted archives Status in tar package in Ubuntu: Triaged Bug description: Hi, Fuzzing tar with checksums disabled reveals a NULL pointer dereference when parsing certain archives that have malformed extended headers. This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't tested Xenial's version. A test case with fixed checksums is attached. To avoid breaking anything that looks inside tar archives, I have converted it to text with xxd. To reproduce: $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar $ tar Oxf gnutar-crash.tar tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr' tar: Malformed extended header: missing length Segmentation fault (core dumped) I have also attached a patch against the latest upstream git and against 1.30 (in Cosmic). This fixes the issue by detecting the null result before it is dereferenced. Regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1810241/+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 1831142] Re: libfreetype6-dev doesn't include freetype-config binary anymore
Ok, thanks, I'll pass this info to libagar if not already under work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1831142 Title: libfreetype6-dev doesn't include freetype-config binary anymore Status in freetype package in Ubuntu: Won't Fix Bug description: freetype-config binary was part of the package before disco. Cannot compile for example libagar anymore with freetype support because the build configuration script needs this. Didn't find the executable with ubuntu package search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1831142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
xnox, it looks like you're missing a "$" in md5sum command from: https://launchpadlibrarian.net/426017250/systemd_240-6ubuntu7_240-6ubuntu8.diff.gz for the -proposed systemd version: /sbin/dhclient-script: 57: /etc/dhcp/dhclient-enter-hooks.d/resolved: Syntax error: "(" unexpected Adding it solved my boot problem (systemd stucks in networking services). cheers o/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Confirmed Status in systemd source package in Disco: Confirmed Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+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 1528822] Re: Installation hangs at password prompt
As stated previously, if su is blocking prompting for a password when run as root, this is a bug in your pam /config/. It is not a bug in the pam package. On a default system there is no problem installing postgresql-common. ** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1528822 Title: Installation hangs at password prompt Status in pam package in Ubuntu: Invalid Status in postgresql-common package in Ubuntu: Invalid Bug description: 1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10) 2) Give Password as requested for the configuration of postgresql-common package. (Entered password is visible.) 3) Hit Enter -> process hangs (Ctrl+C or +D do not work either). 4) Only option to exit apt-get is to kill it and delete lock files manually. Full output of apt-get: ...@...:...$ sudo apt-get install postgresql-9.4 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: postgresql-common postgresql-contrib-9.4 Suggested packages: oidentd ident-server locales-all libdbd-pg-perl The following NEW packages will be installed: postgresql-9.4 postgresql-common postgresql-contrib-9.4 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3'433 kB of archives. After this operation, 14.8 MB of additional disk space will be used. Do you want to continue? [Y/n] y Preconfiguring packages ... Selecting previously unselected package postgresql-common. (Reading database ... 321682 files and directories currently installed.) Preparing to unpack .../postgresql-common_169git1_all.deb ... Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common' Unpacking postgresql-common (169git1) ... Selecting previously unselected package postgresql-9.4. Preparing to unpack .../postgresql-9.4_9.4.5-1_amd64.deb ... Unpacking postgresql-9.4 (9.4.5-1) ... Selecting previously unselected package postgresql-contrib-9.4. Preparing to unpack .../postgresql-contrib-9.4_9.4.5-1_amd64.deb ... Unpacking postgresql-contrib-9.4 (9.4.5-1) ... Processing triggers for man-db (2.7.4-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (225-1ubuntu9) ... Setting up postgresql-common (169git1) ... Password: The configuration via dpkg of postgresql-common also hangs after "Password:" prompt. The password can be entered, but is visible and after hitting enter, nothing happens. Can be aborted by Ctrl+C. $ sudo dpkg --configure -a Setting up postgresql-common (169git1) ... Password: hallo ^CPassword change aborted. dpkg: error processing package postgresql-common (--configure): subprocess installed post-installation script was interrupted dpkg: dependency problems prevent configuration of postgresql-9.4: postgresql-9.4 depends on postgresql-common (>= 142~); however: Package postgresql-common is not configured yet. System: Ubuntu 15.10 Package: postgresql-common Version: 169git1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1528822/+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 1831142] Re: libfreetype6-dev doesn't include freetype-config binary anymore
freetype-config is deprecated and incompatible with multiarch. libagar should be fixed to use pkg-config instead. ** Changed in: freetype (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1831142 Title: libfreetype6-dev doesn't include freetype-config binary anymore Status in freetype package in Ubuntu: Won't Fix Bug description: freetype-config binary was part of the package before disco. Cannot compile for example libagar anymore with freetype support because the build configuration script needs this. Didn't find the executable with ubuntu package search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1831142/+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 1831142] [NEW] libfreetype6-dev doesn't include freetype-config binary anymore
Public bug reported: freetype-config binary was part of the package before disco. Cannot compile for example libagar anymore with freetype support because the build configuration script needs this. Didn't find the executable with ubuntu package search ** Affects: freetype (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1831142 Title: libfreetype6-dev doesn't include freetype-config binary anymore Status in freetype package in Ubuntu: New Bug description: freetype-config binary was part of the package before disco. Cannot compile for example libagar anymore with freetype support because the build configuration script needs this. Didn't find the executable with ubuntu package search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1831142/+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 1528822] Re: Installation hangs at password prompt
I have the same issue in a new install of 18.04 as @pravin.chaudhary How do we fix this? ** Also affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1528822 Title: Installation hangs at password prompt Status in pam package in Ubuntu: New Status in postgresql-common package in Ubuntu: Invalid Bug description: 1) sudo apt-get install postgresql (on a fresh install of Ubuntu 15.10) 2) Give Password as requested for the configuration of postgresql-common package. (Entered password is visible.) 3) Hit Enter -> process hangs (Ctrl+C or +D do not work either). 4) Only option to exit apt-get is to kill it and delete lock files manually. Full output of apt-get: ...@...:...$ sudo apt-get install postgresql-9.4 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: postgresql-common postgresql-contrib-9.4 Suggested packages: oidentd ident-server locales-all libdbd-pg-perl The following NEW packages will be installed: postgresql-9.4 postgresql-common postgresql-contrib-9.4 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3'433 kB of archives. After this operation, 14.8 MB of additional disk space will be used. Do you want to continue? [Y/n] y Preconfiguring packages ... Selecting previously unselected package postgresql-common. (Reading database ... 321682 files and directories currently installed.) Preparing to unpack .../postgresql-common_169git1_all.deb ... Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common' Unpacking postgresql-common (169git1) ... Selecting previously unselected package postgresql-9.4. Preparing to unpack .../postgresql-9.4_9.4.5-1_amd64.deb ... Unpacking postgresql-9.4 (9.4.5-1) ... Selecting previously unselected package postgresql-contrib-9.4. Preparing to unpack .../postgresql-contrib-9.4_9.4.5-1_amd64.deb ... Unpacking postgresql-contrib-9.4 (9.4.5-1) ... Processing triggers for man-db (2.7.4-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (225-1ubuntu9) ... Setting up postgresql-common (169git1) ... Password: The configuration via dpkg of postgresql-common also hangs after "Password:" prompt. The password can be entered, but is visible and after hitting enter, nothing happens. Can be aborted by Ctrl+C. $ sudo dpkg --configure -a Setting up postgresql-common (169git1) ... Password: hallo ^CPassword change aborted. dpkg: error processing package postgresql-common (--configure): subprocess installed post-installation script was interrupted dpkg: dependency problems prevent configuration of postgresql-9.4: postgresql-9.4 depends on postgresql-common (>= 142~); however: Package postgresql-common is not configured yet. System: Ubuntu 15.10 Package: postgresql-common Version: 169git1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1528822/+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 1831116] Re: /usr/lib/software-properties/software-properties-dbus:NameError:/usr/lib/software-properties/software-properties-dbus@68:__init__:__init__
This bug was fixed in the package software-properties - 0.98.4 --- software-properties (0.98.4) eoan; urgency=medium * debian/control: - let software-properties-common depends on python3-requests-unixsocket (lp: #1831116) -- Sebastien Bacher Thu, 30 May 2019 18:09:06 +0200 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- 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/1831116 Title: /usr/lib/software-properties/software-properties- dbus:NameError:/usr/lib/software-properties/software-properties- dbus@68:__init__:__init__ Status in software-properties package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/dc2b1bd7cb0e7a59a8f1da6eaae690df668e98e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1831116/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU for Cosmic sponsored, thanks. ** Changed in: cups (Ubuntu Xenial) Status: New => In Progress ** Changed in: cups (Ubuntu Bionic) Status: New => In Progress ** Changed in: cups (Ubuntu Cosmic) Status: New => In Progress ** Changed in: cups (Ubuntu Disco) Status: New => In Progress -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1768166] Re: Random crashes
Currently ibus-libpinyin FTBFS on bionic-proposed, but this is unrelated to the changes in our package. There seems to be some SRUs ongoing there (particularly one for libio-socket-ssl-perl) that are causing some installability issues for gnome-common. It's a long dependency chain leading there, but yeah. Anyway, I have informed the people driving the other SRU to see what we can do to resolve the issue - maybe it's just transient? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: Fix Committed Status in libpinyin source package in Bionic: Fix Committed Status in ibus-libpinyin source package in Cosmic: Fix Committed Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+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 1829417] Re: When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot
** Description changed: [Impact] 'tracker-miner-f' works a lot when I download with chrome [Fix] tracker-miner-f work with much less intencity [Test Case] 1. Open Chrome - 2. Download http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso + 2. Download http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso (This is happening to me with any .iso file) 3. Open gnome-terminal and run top 4. While the download of OI-hipster-gui-20190511.iso occurs, 'tracker-miner-f' works constantly and intentionally ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.1.2-050102-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 16 12:47:13 2019 InstallationDate: Installed on 2018-12-02 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1829417 Title: When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot Status in tracker package in Ubuntu: New Bug description: [Impact] 'tracker-miner-f' works a lot when I download with chrome [Fix] tracker-miner-f work with much less intencity [Test Case] 1. Open Chrome 2. Download http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso (This is happening to me with any .iso file) 3. Open gnome-terminal and run top 4. While the download of OI-hipster-gui-20190511.iso occurs, 'tracker-miner-f' works constantly and intentionally ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.1.2-050102-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 16 12:47:13 2019 InstallationDate: Installed on 2018-12-02 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1829417/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [ Test case libwww-perl (and deps) regression ] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 1. apt install liblwp-protocol-https-perl 2. enable -proposed 3. apt install libio-socket-ssl-perl libnet-ssleay-perl 4. perl -MLWP::UserAgent -e 'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or die' [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * Deprecated npn extenstion does not exist in TLSv1.3 implementation. * This update bundles python 3.6 and 3.7 point releases + * libnet-ssleay-perl introduces two API changes which carry some risk of regression to consuming applications. The risk is considered small. + - Servers implemented in perl may now raise SIGPIPE in the event of a premature client disconnection. This may be a behavior change in openssl itself but has only been noticed in the libnet-ssleay-perl tests. This may represent a DoS attack against any third-party TLS-using servers implemented in perl if they do not already handle SIGPIPE gracefully. + - The behavior of SSLeay::read() and SSLeay::write() has been changed to NOT retry on short reads/short writes, leading to the perl API more closely matching the C API. There are new ssl_read_all() / ssl_write_all() calls for applications w
[Touch-packages] [Bug 1830353] Re: /usr/bin/software-properties-gtk:AttributeError:_update_availability::get_status:_get_raw_snap
This bug was fixed in the package software-properties - 0.96.24.32.9 --- software-properties (0.96.24.32.9) bionic; urgency=medium * debian/control: - required snapd-glib 1.42 (lp: #1830353) [ Iain Lane ] * softwareproperties/gtk/LivepatchPage.py: - livepatch: Always pass a string to SetLivePatchEnabled (lp: #1830348) [ Corey Bryant ] * cloudarchive: Enable support for the Train Ubuntu Cloud Archive on 18.04 (LP: #1829017). -- Sebastien Bacher Fri, 24 May 2019 17:03:01 +0200 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830353 Title: /usr/bin/software-properties- gtk:AttributeError:_update_availability::get_status:_get_raw_snap Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: * Impact The livepatch tab hits an error when an old gir1.2-snapd-glib is installed * Test case The software-properties -> livepatch tab should load without error * Regression potential The change is only in the Debian packaging to ensure a recent enough version of the snapd-glib binding are installed, just check that the package is installable/that the depends is available - The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.96.24.32.8, the problem page at https://errors.ubuntu.com/problem/063a6452979ec2e97686c6136f1447b4e5442f42 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830353/+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 1829017] Re: [SRU] Enable support for Train Cloud Archive
This bug was fixed in the package software-properties - 0.96.24.32.9 --- software-properties (0.96.24.32.9) bionic; urgency=medium * debian/control: - required snapd-glib 1.42 (lp: #1830353) [ Iain Lane ] * softwareproperties/gtk/LivepatchPage.py: - livepatch: Always pass a string to SetLivePatchEnabled (lp: #1830348) [ Corey Bryant ] * cloudarchive: Enable support for the Train Ubuntu Cloud Archive on 18.04 (LP: #1829017). -- Sebastien Bacher Fri, 24 May 2019 17:03:01 +0200 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1829017 Title: [SRU] Enable support for Train Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Status in software-properties source package in Eoan: Fix Released Bug description: Please add support for: cloud-archive:train cloud-archive:train-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the train cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:train sudo add-apt-repository cloud-archive:train-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829017/+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 1830348] Re: /usr/bin/software-properties-gtk:TypeError:msg_reply_handler:_enabled_reply_handler:__call__:call_async
This bug was fixed in the package software-properties - 0.96.24.32.9 --- software-properties (0.96.24.32.9) bionic; urgency=medium * debian/control: - required snapd-glib 1.42 (lp: #1830353) [ Iain Lane ] * softwareproperties/gtk/LivepatchPage.py: - livepatch: Always pass a string to SetLivePatchEnabled (lp: #1830348) [ Corey Bryant ] * cloudarchive: Enable support for the Train Ubuntu Cloud Archive on 18.04 (LP: #1829017). -- Sebastien Bacher Fri, 24 May 2019 17:03:01 +0200 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830348 Title: /usr/bin/software-properties- gtk:TypeError:msg_reply_handler:_enabled_reply_handler:__call__:call_async Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: * Impact Some livepatch errors case are not handling correctly and leading to having an error report rather than a error message * Test case Unsure how to trigger that livepatch error state, but that can be tested by hacking the source and set the 'token' parameter to the calls to SetLivePatchEnabled() to None Also check that the error reports stop for the new version * Regression potential The change is to use an empty string instead of None on error, since the type was incorrect and that case not working it should regress (it could keep not working if the other type was still not valid though, but that shouldn't be the case) - The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.96.24.32.8, the problem page at https://errors.ubuntu.com/problem/ca90da51d0612253e93b8547563a5d9c7c900104 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830348/+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 1830348] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package has now been 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830348 Title: /usr/bin/software-properties- gtk:TypeError:msg_reply_handler:_enabled_reply_handler:__call__:call_async Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact Some livepatch errors case are not handling correctly and leading to having an error report rather than a error message * Test case Unsure how to trigger that livepatch error state, but that can be tested by hacking the source and set the 'token' parameter to the calls to SetLivePatchEnabled() to None Also check that the error reports stop for the new version * Regression potential The change is to use an empty string instead of None on error, since the type was incorrect and that case not working it should regress (it could keep not working if the other type was still not valid though, but that shouldn't be the case) - The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.96.24.32.8, the problem page at https://errors.ubuntu.com/problem/ca90da51d0612253e93b8547563a5d9c7c900104 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830348/+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 1829017] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package has now been 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1829017 Title: [SRU] Enable support for Train Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Eoan: Fix Released Bug description: Please add support for: cloud-archive:train cloud-archive:train-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the train cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:train sudo add-apt-repository cloud-archive:train-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829017/+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 1830353] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package has now been 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830353 Title: /usr/bin/software-properties- gtk:AttributeError:_update_availability::get_status:_get_raw_snap Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact The livepatch tab hits an error when an old gir1.2-snapd-glib is installed * Test case The software-properties -> livepatch tab should load without error * Regression potential The change is only in the Debian packaging to ensure a recent enough version of the snapd-glib binding are installed, just check that the package is installable/that the depends is available - The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.96.24.32.8, the problem page at https://errors.ubuntu.com/problem/063a6452979ec2e97686c6136f1447b4e5442f42 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830353/+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 1830502] Re: apparmor uses excessive memory leading to oom kill
@Sergio: your issue is different. It is being killed during a kernel operation (sys_write) due to a vmalloc failure, where this bug is occurring during a userspace compile. Please open a new bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1830502 Title: apparmor uses excessive memory leading to oom kill Status in apparmor package in Ubuntu: New Bug description: When attempting to load the profile from comment #7, apparmor uses excessive amounts of memory leading to being killed by the OOM killer and thus the apparmor.service failing. Original bug description: On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my system was unable to finish booting and I had to go into recovery mode and remove a number of files before the system would boot. After doing so I discovered that now the apparmor.service systemd unit always fails to start. I see this in dmesg: [ 1066.975360] Out of memory: Kill process 6799 (apparmor_parser) score 796 or sacrifice child [ 1066.975364] Killed process 6799 (apparmor_parser) total-vm:15057348kB, anon-rss:15046148kB, file-rss:0kB, shmem-rss:0kB [ 1067.406595] oom_reaper: reaped process 6799 (apparmor_parser), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Whenever apparmor.service is attempted to be started by systemd, i.e. either on boot, or later with `systemctl start apparmor`. The log from journalctl doesn't show any actual issues with any profiles just this: -- Reboot -- May 25 17:00:58 systemd[1]: Starting AppArmor initialization... May 25 17:00:58 apparmor[1521]: * Starting AppArmor profiles May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 25 17:01:40 apparmor[1521]:...fail! May 25 17:01:40 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a May 25 17:01:40 systemd[1]: apparmor.service: Failed with result 'exit-code'. May 25 17:01:40 systemd[1]: Failed to start AppArmor initialization. May 25 17:04:53 systemd[1]: Starting AppArmor initialization... May 25 17:04:53 apparmor[4747]: * Starting AppArmor profiles May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 25 17:05:25 apparmor[4747]:...fail! May 25 17:05:25 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a May 25 17:05:25 systemd[1]: apparmor.service: Failed with result 'exit-code'. May 25 17:05:25 systemd[1]: Failed to start AppArmor initialization. I can see that apparmor profiles are active after doing this (using aa-status), but it's still troubling that apparmor runs into an issue without actually saying what the error is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1830502/+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 1768166] Please test proposed package
Hello Ping-Wu, or anyone else affected, Accepted ibus-libpinyin into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ibus- libpinyin/1.11.0-1ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: Fix Committed Status in libpinyin source package in Bionic: Fix Committed Status in ibus-libpinyin source package in Cosmic: Fix Committed Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bu
[Touch-packages] [Bug 1768166] Re: Random crashes
Hello Ping-Wu, or anyone else affected, Accepted ibus-libpinyin into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ibus- libpinyin/1.11.0-1ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ibus-libpinyin (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: ibus-libpinyin (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: Fix Committed Status in libpinyin source package in Bionic: Fix Committed Status in ibus-libpinyin source package in Cosmic: Fix Committed Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator a
[Touch-packages] [Bug 1831116] Re: /usr/lib/software-properties/software-properties-dbus:NameError:/usr/lib/software-properties/software-properties-dbus@68:__init__:__init__
** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Fix Committed -- 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/1831116 Title: /usr/lib/software-properties/software-properties- dbus:NameError:/usr/lib/software-properties/software-properties- dbus@68:__init__:__init__ Status in software-properties package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/dc2b1bd7cb0e7a59a8f1da6eaae690df668e98e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1831116/+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 1831116] [NEW] /usr/lib/software-properties/software-properties-dbus:NameError:/usr/lib/software-properties/software-properties-dbus@68:__init__:__init__
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/dc2b1bd7cb0e7a59a8f1da6eaae690df668e98e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Low Status: Fix Committed ** Tags: bionic disco -- 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/1831116 Title: /usr/lib/software-properties/software-properties- dbus:NameError:/usr/lib/software-properties/software-properties- dbus@68:__init__:__init__ Status in software-properties package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/dc2b1bd7cb0e7a59a8f1da6eaae690df668e98e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1831116/+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 1768166] Please test proposed package
Hello Ping-Wu, or anyone else affected, Accepted libpinyin into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libpinyin/2.2.2-1~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: Fix Committed Status in ibus-libpinyin source package in Cosmic: In Progress Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bugs.launchpad.net/
[Touch-packages] [Bug 1768166] Please test proposed package
Hello Ping-Wu, or anyone else affected, Accepted libpinyin into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libpinyin/2.2.2-1~ubuntu18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libpinyin (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: Fix Committed Status in ibus-libpinyin source package in Cosmic: In Progress Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-
[Touch-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown
** Description changed: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. - When I choose "Power Off", it closes the session screen but then the it displays the red dots who scroll under Ubuntu logo and it never stop completely. + When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive -- 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/1829077 Title: disco 19.04 doesn't shutdown Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: New Status in bash source package in Cosmic: New Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1768166] Re: Random crashes
Hello Ping-Wu, or anyone else affected, Accepted libpinyin into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libpinyin/2.2.2-1ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libpinyin (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: In Progress Status in ibus-libpinyin source package in Cosmic: In Progress Status in libpinyin source package in Cosmic: Fix Committed Bug description: [Impact] ibus-libpinyin has proved to crash far too often. One or more files in ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that directory allows the user to keep using ibus-libpinyin. In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are present, and the number of crashes has been reduced significantly: https://errors.ubuntu.com/?package=ibus-libpinyin&period=month Upstream ChangeLog ibus-libpinyin: -- version 1.11.0 * fixes keypad decimal * fixes emoji candidates * support configurable opencc config version 1.10.92 * fixes Enter handling version 1.10.91 * support ime.register_trigger in lua extension * support predicted candidates * support emoji input version 1.10.0 * bug fixes version 1.9.91 * migrate to use GSettings * fixes lyx short cut issue version 1.9.3 * translate input method name in ibus menu Upstream ChangeLog libpinyin: - version 2.2.2 * minor fixes version 2.2.1 * fixes predicted candidates version 2.2.0 * bug fixes The proposal is to backport the disco versions of those packages to bionic and cosmic in an attempt to prevent crashes. Proposed uploads are available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin [Test Case] * Install from {bionic,cosmic}-proposed: - libpinyin13 - libpinyin-data - ibus-libpinyin * Use "Intelligent Pinyin" for typing and confirm that no new issues show up when doing so. (This is apparently not a confirmation that the upload really fixes the bug. To compensate for that, we will await testing of the -proposed packages by a few Chinese users before considering the uploads verified.) Reverse dependencies Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on packages belonging to the libpinyin source package. So additional test measures are: * Install fcitx-libpinyin and ibus-zhuyin. * Use both those tools for typing Chinese, and confirm that you don't observe any adverse effects of the libpinyin upgrade. [Regression Potential] The changes are mostly bug fixes, so the regression risk should be limited. Also consider that the starting point is a rather unstable functionality. NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get as much testing as possible. There do not seem to be too many risky changes carried, but such jumps in upstream versions always carry some regression-risk. [Original description] I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update t
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hello Dimitri, or anyone else affected, Accepted libio-socket-ssl-perl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libio-socket-ssl-perl/2.060-3~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libio-socket-ssl-perl (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in libwww-perl package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: In Progress Status in libio-socket-ssl-perl source package in Bionic: Fix Committed Status in libnet-ssleay-perl source package in Bionic: In Progress Status in libwww-perl source package in Bionic: Fix Committed Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Fix Committed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [ Test case libwww-perl (and deps) regression ] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 1. apt install liblwp-protocol-https-perl 2. enable -proposed 3. apt install libio-socket-ssl-perl libnet-ssleay-perl 4. perl -MLWP::UserAgent -e 'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or die'
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hello Dimitri, or anyone else affected, Accepted libwww-perl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libwww- perl/6.31-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [ Test case libwww-perl (and deps) regression ] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 - apt install liblwp-protocol-https-perl libio-socket-ssl-perl libnet- - ssleay-perl - - perl -MLWP::UserAgent -e - 'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or - die' + 1. apt install liblwp-protocol-https-perl + 2. enable -proposed + 3. apt install libio-socket-ssl-perl libnet-ssleay-perl + 4. perl -MLWP::UserAgent -e 'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or die' [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of th
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+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 1831102] [NEW] /usr/bin/zeitgeist-daemon:6:____lambda5__glog_func:g_logv:g_log:zeitgeist_data_source_registry_extension_name_owner_changed:_zeitgeist_data_source_registry_extensi
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/41868297bfe1403326cb0c46ad58ef663e114286 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco kylin-17.10 kylin-18.04 xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1831102 Title: /usr/bin/zeitgeist- daemon:6:lambda5__glog_func:g_logv:g_log:zeitgeist_data_source_registry_extension_name_owner_changed:_zeitgeist_data_source_registry_extension_name_owner_changed_gd_bus_signal_callback Status in zeitgeist package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/41868297bfe1403326cb0c46ad58ef663e114286 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1831102/+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 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
** Changed in: bash (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: bash (Ubuntu Cosmic) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: bash (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: New Status in bash source package in Cosmic: New Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1831101] [NEW] rsync with remote sudo fails over ssh/pki with protocol mismatch error
Public bug reported: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude --delete --link-dest=../$lastdt /etc $dest/$dt -- The [redacted] output is opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 (20 args) OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xxx [192.168.1.120] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/user/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug1: Authenticating to xxx:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: MAC: compression: none debug1: kex: client->server cipher: MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: xxx Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known hosts. debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa debug1: Server accepts key: xxx debug1: Authentication succeeded (publickey). Authenticated to xxx ([192.168.1.120]:22). debug1: channel 0: new [client-session] debug1: Requesting debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype want_reply 0 debug1: tty_make_modes: no fd or tio debug1: Sending environment. debug1: Sending env LANG = en_GB.UTF-8 debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2] [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2) --- /etc/sudoers contains user ALL= NOPASSWD:/usr/bin/rsync ...which I have tried placing above (as is the default) and below lines beginning %admin and %sudo and the space in "ALL= NOPASSWD..." doesn't seem to make any difference I followed the instructions at https://www.digitalocean.com/community/tutorials/how-to-copy-files-with- rsync-over-ssh https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the- destination-machine ...which worked on 16.04, so I wonder if there may be a bug, although grateful for any other suggestions, as I am unsure how to debug/investigate further ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: rsync ** Tags added: rsync -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1831101 Title: rsync with remote sudo fails over ssh/pki with protocol mismatch error Status in rsync package in Ubuntu: New Bug description: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsyn
[Touch-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1829077 Title: disco 19.04 doesn't shutdown Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then the it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Thanks Till. I've fixed cosmic debdiff, sorry about the mistake. ** Patch removed: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff ** Patch added: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267712/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff ** Changed in: cups (Ubuntu Xenial) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) ** Changed in: cups (Ubuntu Cosmic) Importance: Undecided => Medium -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1831079] [NEW] Documentation bug for pam_userdb
Public bug reported: The man page for pam_userdb(8) has an incorrect example > auth sufficient pam_userdb.so icase db=/etc/dbtest.db should be > auth sufficient pam_userdb.so icase db=/etc/dbtest It should also be mentioned in the options that ".db" will be added to the value of db. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Microsoft 4.4.0-17134.706-Microsoft 4.4.35 Uname: Linux 4.4.0-17134-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu May 30 13:33:25 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1831079 Title: Documentation bug for pam_userdb Status in pam package in Ubuntu: New Bug description: The man page for pam_userdb(8) has an incorrect example > auth sufficient pam_userdb.so icase db=/etc/dbtest.db should be > auth sufficient pam_userdb.so icase db=/etc/dbtest It should also be mentioned in the options that ".db" will be added to the value of db. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Microsoft 4.4.0-17134.706-Microsoft 4.4.35 Uname: Linux 4.4.0-17134-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu May 30 13:33:25 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1831079/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
I have sponsored the Xenial SRU now, but the one for Cosmic is missing the addition of the patch to debian/patches/series. -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 + [ Test case libwww-perl (and deps) regression ] + + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 + + apt install liblwp-protocol-https-perl libio-socket-ssl-perl libnet- + ssleay-perl + + perl -MLWP::UserAgent -e + 'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or + die' + [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. - * Deprecated npn extenstion does not exist in TLSv1.3 implementation. + * Deprecated npn extenstion does not exist in TLSv1.3 implementation. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 [Autopkgtest Regressions] dovecot/armhf - flakey libnet-ssleay-perl - awaiting sru accept into proposed of libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and versioned breaks. linux* - rebuild testcases passes (for some edge flavours the build fails in non-ssl portions of the buil
[Touch-packages] [Bug 1830502] Re: apparmor uses excessive memory leading to oom kill
Hi, running the snapd tests on i386 I see the following error that could be related to this. It is failing with pc-kernel on beta and candidate but I coun't reproduce it with the version on stable. > snap list Name VersionRev Tracking Publisher Notes core 16-2.39.1 7122 beta canonical* core pc 16.04-0.10 34candidate canonical* gadget pc-kernel 4.4.0-149.175 219 candidate canonical* kernel Logs: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: vmap allocation for size 73728 failed: use vmalloc= to increase size. May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: vmalloc: allocation failure: 68497 bytes May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: apparmor_parser: page allocation failure: order:0, mode:0x24000c2 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: CPU: 1 PID: 23415 Comm: apparmor_parser Not tainted 4.4.0-149-generic #175-Ubuntu May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: c1b15967 70e2bd9c 0286 d0cf7e00 c13c12ef c1a1ce6c 0001 d0cf7e30 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: c11821b6 c1a1b220 f479a700 024000c2 d0cf7e44 c1a1ce6c d0cf7e18 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: 70e2bd9c 00010b91 d0cf7e60 c11ba86f 024000c2 c1a1ce6c May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Call Trace: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] dump_stack+0x58/0x79 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] warn_alloc_failed+0xd6/0x110 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vmalloc_node_range+0x1ef/0x210 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vmalloc_node+0x66/0x70 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] vmalloc+0x38/0x40 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] aa_simple_write_to_buffer+0x34/0x90 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] policy_update+0x73/0x230 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? security_file_permission+0x3e/0xd0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] profile_replace+0x98/0xe0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? policy_update+0x230/0x230 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vfs_write+0x22/0x50 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] vfs_write+0x8c/0x1b0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] SyS_write+0x51/0xb0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] do_fast_syscall_32+0x9f/0x190 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] sysenter_past_esp+0x3d/0x61 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Mem-Info: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: active_anon:10318 inactive_anon:1512 isolated_anon:0 May 30 03:57:34 localhost.localdomain snapd[23208]: active_file:77754 inactive_file:23998 isolated_file:0 May 30 03:57:34 localhost.localdomain snapd[23208]: unevictable:0 dirty:551 writeback:0 unstable:0 May 30 03:57:34 localhost.localdomain snapd[23208]: slab_reclaimable:7394 slab_unreclaimable:13711 May 30 03:57:34 localh
[Touch-packages] [Bug 1831074] [NEW] In high fidelity playback, front right side of headset doesn't work
Public bug reported: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1831074 Title: In high fidelity playback, front right side of headset doesn't work Status in bluez package in Ubuntu: New Bug description: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touc
[Touch-packages] [Bug 1778695] Re: ristretto ignores cr2 files
** Changed in: file (Ubuntu) Status: New => Invalid ** Changed in: ristretto (Ubuntu) Importance: Undecided => Low ** Changed in: ristretto (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1778695 Title: ristretto ignores cr2 files Status in file package in Ubuntu: Invalid Status in ristretto package in Ubuntu: Fix Committed Bug description: Ristretto does not show canon .cr2 files, neither on 16.04.4 nor on 18.04. For 16.04: lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 apt-cache policy ristretto ristretto: Installed: 0.8.0-1 Candidate: 0.8.0-1 Version table: *** 0.8.0-1 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status for 18.04 lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy ristretto ristretto: Installed: 0.8.2-1ubuntu1 Candidate: 0.8.2-1ubuntu1 Version table: *** 0.8.2-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1778695/+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 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
** Tags removed: ddstreet-next -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Cosmic: Invalid Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Committed Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+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 1647692] Re: Need to exclude directories
Note that you can prevent mediascanner from scanning a directory by putting the file ".nomedia" in it. This will obviously only work for OSM-maps, as CD covers usually are located in directories with music files that mediascanner needs find. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1647692 Title: Need to exclude directories Status in gallery-app package in Ubuntu: New Bug description: The gallery-app shows all pictures on the phone by default. If you put many music files incl. CD-Covers or OSM-cards (thousands of files) for uNav on the SD-card, the gallery-app becomes very slow or nearly unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1647692/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Tags removed: ddstreet-next ** Description changed: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. + + -- + sru template for systemd upload: + + [impact] + buffer overflow can cause memory corruption; this is seen in failed autopkgtests + + [test case] + see comment 6 + + [regression potential] + the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in udisks2 source package in Bionic: Invalid Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: In Progress Status in udisks2 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: In Progress Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in udisks2 source package in Eoan: Invalid Status in systemd package in Debian: Unknown Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1825997] Re: boot-smoke fails due to running jobs
** Tags removed: ddstreet-next -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Cosmic. ** Patch added: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Also affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1827099] Re: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1827099 Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: Confirmed Bug description: Crash at the end of upgrade to 19.04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue Apr 30 21:07:35 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-28 (1280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: shared-mime-info Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 1827099] Re: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned
ditto upgrading in two steps bionic->cosmic->disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1827099 Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned Status in shared-mime-info package in Ubuntu: Confirmed Bug description: Crash at the end of upgrade to 19.04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue Apr 30 21:07:35 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-28 (1280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: shared-mime-info Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
Uploaded patched systemd to b/c queues. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in network-manager source package in Cosmic: New Status in systemd source package in Cosmic: In Progress Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Xenial. ** Patch added: "xenial_cups_2.1.3-4ubuntu0.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267662/+files/xenial_cups_2.1.3-4ubuntu0.9.debdiff -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: libreoffice (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: libreoffice-l10n (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 icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If t
[Touch-packages] [Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
The commit seems reasonable for a SRU. Could you maybe add an example/testcase to the bug that could be used for the SRU process? (we need to be able to verify the problem and the solution) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories Status in libarchive package in Ubuntu: New Bug description: The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is the only version that presents the problem. This version has a known problem when reading file entries in ZIP files, where it incorrectly identifies directories and files entries. It has been confirmed that the previous and following versions (3.3.1+) do not have this problem and the library handles the ZIP files correctly. Is it possible to include a newer version of libarchive (3.3.1+) in Bionic? This problem is seriously affecting some of our systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1791405] Re: bluetooth always in discoverable mode (security issue)
** No longer affects: bluez (Ubuntu Bionic) ** No longer affects: bluez (Ubuntu Cosmic) ** No longer affects: bluez (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Status in gnome-bluetooth source package in Cosmic: Fix Released Status in gnome-bluetooth source package in Disco: Fix Released Status in bluez source package in Eoan: Fix Committed Status in gnome-bluetooth package in Fedora: Won't Fix Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Sponsored SRUs for Bionic and Disco. -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1831042] Re: xrandr not working on wayland
Wayland support is provided by the 'mutter' project to gnome-shell. And X support for clients like xrandr is provided by 'Xwayland' which is built from the 'xorg-server' source. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831042 Title: xrandr not working on wayland Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Using xrandr to turn screen when switching to tablet mode on laptop (using different orientation). This not working when on wayland xrandr -o normal xrandr -o inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1831042/+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 1831040] Re: sudo apps not working with wayland
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1652282, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1652282 Xwayland not using XAUTHORITY, prevents root applications from connecting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831040 Title: sudo apps not working with wayland Status in gnome-session package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: When using wayland - cannot use sudo applications that asks for admin privileges such as synaptic. Program ends without showing any errors. Not asking for password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1831040/+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 1831042] [NEW] xrandr not working on wayland
Public bug reported: Using xrandr to turn screen when switching to tablet mode on laptop (using different orientation). This not working when on wayland xrandr -o normal xrandr -o inverted ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: Using xrandr to turn screen when switching to tablet mode on laptop (using different orientation). This not working when on wayland + + xrandr -o normal + xrandr -o inverted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831042 Title: xrandr not working on wayland Status in wayland package in Ubuntu: New Bug description: Using xrandr to turn screen when switching to tablet mode on laptop (using different orientation). This not working when on wayland xrandr -o normal xrandr -o inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1831042/+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 1831040] [NEW] sudo apps not working with wayland
Public bug reported: When using wayland - cannot use sudo applications that asks for admin privileges such as synaptic. Program ends without showing any errors. Not asking for password. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831040 Title: sudo apps not working with wayland Status in wayland package in Ubuntu: New Bug description: When using wayland - cannot use sudo applications that asks for admin privileges such as synaptic. Program ends without showing any errors. Not asking for password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1831040/+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 1831039] Re: wayland onscreen keyboard not open
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1831039 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: bionic ** Tags added: osk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: wayland onscreen keyboard not open Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831039/+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 1831037] Re: not working list
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1831037 Title: not working list Status in Ubuntu: Incomplete Bug description: thunderbird - send email keyboard from laptop no physical shut down or reeboot tried all the information online have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 30 11:02:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0938] InstallationDate: Installed on 2015-10-28 (1309 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-311 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-311 dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: BayTrail dmi.product.name: Aspire ES1-311 dmi.product.version: V1.11 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 21 13:03:46 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1831037/+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 1831039] [NEW] wayland onscreen keyboard not open
Public bug reported: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic bugs osk wayland ** Project changed: launchpad => wayland (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: wayland onscreen keyboard not open Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831039/+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 1831039] [NEW] wayland onscreen keyboard not open
You have been subscribed to a public bug: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: bugs wayland -- wayland onscreen keyboard not open https://bugs.launchpad.net/bugs/1831039 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Discussion upstream: https://lists.cups.org/pipermail/cups/2019-May/074657.html ** Tags added: rls-ee-incoming -- 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/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+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 1831037] [NEW] not working list
Public bug reported: thunderbird - send email keyboard from laptop no physical shut down or reeboot tried all the information online have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 30 11:02:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0938] InstallationDate: Installed on 2015-10-28 (1309 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-311 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-311 dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: BayTrail dmi.product.name: Aspire ES1-311 dmi.product.version: V1.11 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 21 13:03:46 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- 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/1831037 Title: not working list Status in xorg package in Ubuntu: New Bug description: thunderbird - send email keyboard from laptop no physical shut down or reeboot tried all the information online have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 30 11:02:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0938] InstallationDate: Installed on 2015-10-28 (1309 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-311 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libreoffice (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 icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Committed Status in libreoffice-l10n source package in Xenial: Fix Committed Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If
[Touch-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
This bug was fixed in the package evolution-data-server - 3.30.5-0ubuntu0.18.10.1 --- evolution-data-server (3.30.5-0ubuntu0.18.10.1) cosmic; urgency=medium * New upstream version (lp: #1815882) - include fix for Kopano IMAP servers (lp: #1813268) * debian/libebackend-1.2-10.symbols: - updated for new symbols -- Sebastien Bacher Wed, 13 Feb 2019 10:27:48 +0100 ** Changed in: evolution-data-server (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Released Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+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 1815882] Re: Update evolution-data-server to 3.30.5
This bug was fixed in the package evolution-data-server - 3.30.5-0ubuntu0.18.10.1 --- evolution-data-server (3.30.5-0ubuntu0.18.10.1) cosmic; urgency=medium * New upstream version (lp: #1815882) - include fix for Kopano IMAP servers (lp: #1813268) * debian/libebackend-1.2-10.symbols: - updated for new symbols -- Sebastien Bacher Wed, 13 Feb 2019 10:27:48 +0100 ** Changed in: evolution-data-server (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Released Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+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 1813268] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Released Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+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 1815882] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Released Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
@sponsors: Eoan already has the fix from Debian. -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Disco ** Patch added: "disco_cups_2.2.10-4ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267599/+files/disco_cups_2.2.10-4ubuntu2.debdiff -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
The patch doesn't apply cleanly to Xenial, working on backport. ** Changed in: cups (Ubuntu Xenial) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: cups (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Disco) Importance: Undecided => Medium -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Bionic ** Patch added: "bionic_cups_2.2.7-1ubuntu2.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267600/+files/bionic_cups_2.2.7-1ubuntu2.6.debdiff -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1831021] Re: Extremely high memory consumption under heavy workload
** Description changed: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: - After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. + After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cupsd killed by OOM killer. -- 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/1831021 Title: Extremely high memory consumption under heavy workload Status in cups package in Ubuntu: New Bug description: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cupsd killed by OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+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 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
Today I got same issue and @pujanm's suggestion is solved the problem. # apt-get update Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Get:3 https://repo.skype.com/deb stable InRelease [4.487 B] Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease Get:5 http://archive.canonical.com/ubuntu bionic InRelease [10,2 kB] Ign:6 http://repo.vivaldi.com/stable/deb stable InRelease Get:7 http://dl.google.com/linux/chrome/deb stable Release [943 B] Get:8 http://repo.vivaldi.com/stable/deb stable Release [3.831 B] Get:9 http://repo.vivaldi.com/stable/deb stable Release.gpg [833 B] Get:10 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2.320 B] Get:11 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Ign:13 http://packages.linuxmint.com tessa InRelease Get:14 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [265 kB] Get:15 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2.320 B] Get:16 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1.276 B] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Get:18 https://repo.skype.com/deb stable/main amd64 Packages [2.274 B] Get:19 http://repo.vivaldi.com/stable/deb stable/main i386 Packages [1.193 B] Get:20 http://packages.linuxmint.com tessa Release [24,1 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1.007 kB] Ign:22 https://artifacts.elastic.co/packages/7.x/apt stable InRelease Get:23 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1.197 B]
[Touch-packages] [Bug 1831025] Re: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
Dear Adam, the log you provided does not seem to indicate an issue with acquiring data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does not support your Ubuntu release (18.04 / bionic). So this appears to not be a bug, just use of an incompatible PPA, making this more of a support request. I'm therefore changing the status to "invalid" - should I have missed relevant facts you are welcome to undo this change. Should you need further support with this, please consider one of the following options: https://www.ubuntu.com/support https://www.ubuntu.com/support/community-support Thanks, Tom -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1831025 Title: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list Status in apt package in Ubuntu: Invalid Bug description: The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu- keepass-bionic.list: deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main causes sudo apt update to fail for this entry with the error: 404 Not Found [IP: 91.189.95.83 80] Full transcript: $ sudo apt update Hit:1 http://deb.playonlinux.com bionic InRelease Hit:2 http://pl.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/bookworm-team/bookworm/ubuntu bionic InRelease Hit:4 http://pl.archive.ubuntu.com/ubuntu bionic-updates InRelease Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease Hit:6 http://pl.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 Release Hit:8 http://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease Hit:9 http://pl.archive.ubuntu.com/ubuntu bionic-proposed InRelease Ign:10 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic InRelease Hit:11 https://repo.skype.com/deb stable InRelease Hit:12 http://ppa.launchpad.net/elementary-os/stable/ubuntu bionic InRelease Hit:13 http://ppa.launchpad.net/fixnix/netspeed/ubuntu bionic InRelease Hit:14 http://dl.winehq.org/wine-builds/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:16 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease Hit:18 http://ppa.launchpad.net/noobslab/themes/ubuntu bionic InRelease Hit:20 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease Hit:21 http://ppa.launchpad.net/unity7maintainers/unity7-desktop/ubuntu bionic InRelease Hit:22 http://ppa.launchpad.net/yktooo/ppa/ubuntu bionic InRelease Err:23 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release 404 Not Found
[Touch-packages] [Bug 1831025] Re: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
That's the wrong source, please read the error message carefully - the solaar ppa for which the error occurs does not provide any bionic packages. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1831025 Title: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list Status in apt package in Ubuntu: Invalid Bug description: The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu- keepass-bionic.list: deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main causes sudo apt update to fail for this entry with the error: 404 Not Found [IP: 91.189.95.83 80] Full transcript: $ sudo apt update Hit:1 http://deb.playonlinux.com bionic InRelease Hit:2 http://pl.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/bookworm-team/bookworm/ubuntu bionic InRelease Hit:4 http://pl.archive.ubuntu.com/ubuntu bionic-updates InRelease Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease Hit:6 http://pl.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 Release Hit:8 http://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease Hit:9 http://pl.archive.ubuntu.com/ubuntu bionic-proposed InRelease Ign:10 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic InRelease Hit:11 https://repo.skype.com/deb stable InRelease Hit:12 http://ppa.launchpad.net/elementary-os/stable/ubuntu bionic InRelease Hit:13 http://ppa.launchpad.net/fixnix/netspeed/ubuntu bionic InRelease Hit:14 http://dl.winehq.org/wine-builds/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:16 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease Hit:18 http://ppa.launchpad.net/noobslab/themes/ubuntu bionic InRelease Hit:20 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease Hit:21 http://ppa.launchpad.net/unity7maintainers/unity7-desktop/ubuntu bionic InRelease Hit:22 http://ppa.launchpad.net/yktooo/ppa/ubuntu bionic InRelease Err:23 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release 404 Not Found [IP: 91.189.95.83 80] Ign:17 https://attic.owncloud.com/org/download/repositories/10.0/Ubuntu_18.04 InRelease Hit:24 http://download.owncloud.org/download/repositories/10.0/Ubuntu_18.04 Release Hit:26 http://security.ubuntu.com/ubuntu bionic-security InRelease Reading package lists... Done E: The repository 'http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Description changed: + [Impact] + + The documentation allows the following types of arguments for the PreserveJobHistory parameter: + PreserveJobHistory Yes + PreserveJobHistory No + PreserveJobHistory seconds + + The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . + + [Test Case] + + * Set PreserveJobHistory to 300. + * Schedule a job for printing. + * Check the error_log. + + Expected result: + Job is save for at least 300 seconds. + + Actual results: + Job is immediately removed from history. + + [Regression Potential] + + * With the fix the jobs will be saved longer than before, so in tight + conditions (low disk space) and heavy workload it may affect memory/disk + space consumption and lead to running out of free space in worst case. + + [Other Info] + + * Original bug description: + 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: - Installed: 2.1.3-4ubuntu0.3 - Candidate: 2.1.3-4ubuntu0.3 - Version table: - *** 2.1.3-4ubuntu0.3 500 - 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + Installed: 2.1.3-4ubuntu0.3 + Candidate: 2.1.3-4ubuntu0.3 + Version table: + *** 2.1.3-4ubuntu0.3 500 + 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf - PreserveJobFiles Yes + PreserveJobFiles Yes -PreserveJobFiles No + PreserveJobFiles No -PreserveJobFiles seconds - Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved - for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). + PreserveJobFiles seconds + Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved + for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). -PreserveJobHistory Yes + PreserveJobHistory Yes -PreserveJobHistory No + PreserveJobHistory No -PreserveJobHistory seconds - Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for - the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default - is "Yes". + PreserveJobHistory seconds + Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for + the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default + is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 - Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... ** Changed in: cups (Ubuntu) Importance: Undecided => Medium ** Also affects: cups (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual r
[Touch-packages] [Bug 1831025] [NEW] apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
Public bug reported: The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu- keepass-bionic.list: deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main causes sudo apt update to fail for this entry with the error: 404 Not Found [IP: 91.189.95.83 80] Full transcript: $ sudo apt update Hit:1 http://deb.playonlinux.com bionic InRelease Hit:2 http://pl.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/bookworm-team/bookworm/ubuntu bionic InRelease Hit:4 http://pl.archive.ubuntu.com/ubuntu bionic-updates InRelease Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease Hit:6 http://pl.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 Release Hit:8 http://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease Hit:9 http://pl.archive.ubuntu.com/ubuntu bionic-proposed InRelease Ign:10 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic InRelease Hit:11 https://repo.skype.com/deb stable InRelease Hit:12 http://ppa.launchpad.net/elementary-os/stable/ubuntu bionic InRelease Hit:13 http://ppa.launchpad.net/fixnix/netspeed/ubuntu bionic InRelease Hit:14 http://dl.winehq.org/wine-builds/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:16 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease Hit:18 http://ppa.launchpad.net/noobslab/themes/ubuntu bionic InRelease Hit:20 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease Hit:21 http://ppa.launchpad.net/unity7maintainers/unity7-desktop/ubuntu bionic InRelease Hit:22 http://ppa.launchpad.net/yktooo/ppa/ubuntu bionic InRelease Err:23 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release 404 Not Found [IP: 91.189.95.83 80] Ign:17 https://attic.owncloud.com/org/download/repositories/10.0/Ubuntu_18.04 InRelease Hit:24 http://download.owncloud.org/download/repositories/10.0/Ubuntu_18.04 Release Hit:26 http://security.ubuntu.com/ubuntu bionic-security InRelease Reading package lists... Done E: The repository 'http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Possible cause: three dots in the source confused the parser and it improperly handles TCP port. Please note, that when I connect through acng with Acquire::http::Proxy "http://192.168.10.2:3142";; the error turns into ` 404 Not Found [IP: 192.168.10.2 3142]`. Further info: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic $ uname -a Linux n56vz-bionic 4
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This has been fixed in 19.10 for cups 2.2.10-6 (backport from upstream). ** Changed in: cups (Ubuntu) Status: Confirmed => Fix Released -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Disco: New Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
Thanks for reporting this issue - this would appear to have potential security implications, however as it is already public I see no reason to keep this private - if a CVE were to be assigned then this could be fixed via a security update by the security team, otherwise this would be fixed via the normal SRU process[1]. As such, please feel free to file a CVE request with MITRE[2] and if one is assigned, please update this bug report with the CVE ID and we can fix it via the security team. [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://cve.mitre.org/cve/request_id.html ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories Status in libarchive package in Ubuntu: New Bug description: The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is the only version that presents the problem. This version has a known problem when reading file entries in ZIP files, where it incorrectly identifies directories and files entries. It has been confirmed that the previous and following versions (3.3.1+) do not have this problem and the library handles the ZIP files correctly. Is it possible to include a newer version of libarchive (3.3.1+) in Bionic? This problem is seriously affecting some of our systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+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 1831021] Re: Extremely high memory consumption under heavy workload
After some analysis I believe the very high default value of LogDebugHistory (9) is to blame for this (attaching massif report from the test case). With a high number of jobs it's very easy to get hunderds-thousands of messages in LogDebugHistory which in turn will lead to enormous memory consumption, e.g. 4 jobs * 2000 lines * (16 bytes for cupsd_joblog_t structure + 50-60 chars per message on average) - 5.66 GB. After setting LogDebugHistory to 0 the memory consumption never exceeded 300 MB in my tests under the same heavy load. That's a very significant difference. The possible workarounds: 1. Decrease LogDebugHistory to a low value (even to 0, upstream it's set to 200 by default). 2. Change LogLevel to debug (it will slow down cupsd operation significantly, but at the price of lower memory consumption as the LogDebugHistory is unused). 3. Make sure jobs are cleaned periodically by setting e.g. PreserveJobHistory 300. I am wondering what was the rationale behind increasing LogDebugHistory to such a high value. ** Attachment added: "massif.out.xz" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+attachment/5267574/+files/massif.out.xz -- 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/1831021 Title: Extremely high memory consumption under heavy workload Status in cups package in Ubuntu: New Bug description: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+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 1831021] [NEW] Extremely high memory consumption under heavy workload
Public bug reported: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1831021 Title: Extremely high memory consumption under heavy workload Status in cups package in Ubuntu: New Bug description: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+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