[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Dear ubuntu staffs, installing new softwares in my ubutu I am persistently face with error as below: dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): installed systemd-shim package post-removal script subprocess returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) please help me solve this problem. Thanks in advance for your help ** Changed in: systemd-shim (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: New Status in systemd-shim source package in Saucy: Won't Fix Status in systemd source package in Trusty: Confirmed Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+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 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.
The speaker has the crackle noise. -- 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/1826730 Title: [ASUS X555YI] audio crackle when the sound a little loud. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826730/+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 1826931] Re: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:am
you should've done a ppa-purge first, and get rid of the padoka ppa packages before upgrade ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1826931 Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 Status in mesa package in Ubuntu: Invalid Bug description: I was doing do-release-upgrade from terminal but somehow the process stopped. I'm stuck on 18.10 and when I do do-release-upgrade it wants me to update all packages before distro upgrading. It tries to download packages from the 19.04 repo ProblemType: Package DistroRelease: Ubuntu 19.04 Package: mesa-common-dev 19.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompositorRunning: None Date: Mon Apr 29 22:28:32 2019 DistUpgraded: 2019-04-29 22:18:48,041 DEBUG inhibit gnome-session idle DistroCodename: disco DistroVariant: ubuntu DuplicateSignature: package:mesa-common-dev:19.0.2-1ubuntu1 Unpacking mesa-common-dev:amd64 (19.0.2-1ubuntu1) over (19.0.1-0~c~padoka0) ... dpkg: error processing archive /tmp/apt-dpkg-install-eeRqan/097-mesa-common-dev_19.0.2-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 ErrorMessage: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake GT2 [HD Graphics 520] [1558:2425] InstallationDate: Installed on 2019-03-13 (46 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b551 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N24_25JU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=7e8a7184-5a6a-41bd-8f32-b0efd253c9d1 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.7.4 SourcePackage: mesa Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 UpgradeStatus: Upgraded to disco on 2019-04-29 (0 days ago) dmi.bios.date: 03/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/31/2016:svnPCSpecialistLimited:pnN24_25JU:pvrNotApplicable:rvnCLEVO:rnN24_25JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1826931/+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 1808344] Re: Various bugs printing pdf files
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1808344 Title: Various bugs printing pdf files Status in cups package in Ubuntu: Expired Bug description: I want to report multiple issues encountered so far on Ubuntu 18.10 regarding printing PDF files. My configuration: - Computer: Dell XPS 15 9530 - OS: Ubuntu 18.10 - Printer: Samsung M2825ND Xpress Mono Laser Printer - PDF Readers Tested: Various (Evince, Foxit, Okular) - PDF Creator Tested: Word, LibreOffice, GhostScript, PDFTex, Acrobat PDFMaker, ... - PDF Sizes Tested: Various - PDF Versions Tested: Various Issues: - Printing 1 page per physical page encounter a lot problems while printing 2 pages per physical page produces issues less often - Sometimes playing around with print setting (such as scaling, centering) solves the issue sometimes it creates it and sometimes does nothing - Printing calc file directly from LibreOffice is not possible Error: - PCL-6 error (don't remember the exact code right now but can provide it if needed) Notes: - My guess is that this is an error related to the printer drivers but since I don't have another printer to test on can't verify. - Another guess is that the PDF produces PDF that use feature that are not properly handled on linux - Turning Markdown text to PDF using PDFlatex causes a printing error whereas turning the same Markdown to html and printing through Chrome causes no issue - If you need more logs please instruct me what I need to to help ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 13:35:13 2018 InstallationDate: Installed on 2018-09-21 (82 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180920) Lpstat: device for M262x-282x: usb://Samsung/M262x%20282x%20Series?serial=ZD2JBJCF6000LMA device for MG3500-series: usb://Canon/MG3500%20series?serial=68152B&interface=1 MachineType: Dell Inc. XPS 15 9530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M262x-282x.ppd', '/etc/cups/ppd/MG3500-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M262x-282x.ppd: Permission denied grep: /etc/cups/ppd/MG3500-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=41f390ce-33d0-4b6a-96a1-fef284448f69 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd01/29/2018:svnDellInc.:pnXPS159530:pvrA10:rvnDellInc.:rnXPS159530:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.sku: XPS 15 9530 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1808344/+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 1791417] Re: Sound bug ubuntu 18.04
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1791417 Title: Sound bug ubuntu 18.04 Status in alsa-driver package in Ubuntu: Expired Bug description: wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh --2018-09-07 12:24:00-- http://www.alsa-project.org/alsa-info.sh Resolving www.alsa-project.org (www.alsa-project.org)... 77.48.224.243 Connecting to www.alsa-project.org (www.alsa-project.org)|77.48.224.243|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh [following] --2018-09-07 12:24:00-- http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh Resolving git.alsa-project.org (git.alsa-project.org)... 77.48.224.243 Connecting to git.alsa-project.org (git.alsa-project.org)|77.48.224.243|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-sh] Saving to: ‘alsa-info.sh’ alsa-info.sh[ <=> ] 28.03K 170KB/sin 0.2s 2018-09-07 12:24:01 (170 KB/s) - ‘alsa-info.sh’ saved [28707] ALSA Information Script v 0.4.64 This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See './alsa-info.sh --help' for command line options. Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa- project.org/db/?f=84ba91e70cc537608d8ffa04c5ec05a08bcf1ed6 Please inform the person helping you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1791417/+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 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.
There are 3 output devices: speaker, headphone and HDMI audio, which one has this crackle noise issue? -- 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/1826730 Title: [ASUS X555YI] audio crackle when the sound a little loud. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826730/+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 1826968] [NEW] tzdata package contains invalid entry for Asia/Novosibirsk
Public bug reported: Ubuntu version: 16.04.6 Problem: in the latest release of tzdata (2019a-0ubuntu0.16.04) the entry for Asia/Novosibirsk consists of text file with the below line only: Asia/Novosibirsk Apart from not working as /etc/localtime, it also creates cryptic errors in other packages (such as PHP complaining on invalid date/time database). After I replaced the above file with the one from Ubuntu 18.04.2 tzdata's latest release, the error was gone. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1826968 Title: tzdata package contains invalid entry for Asia/Novosibirsk Status in tzdata package in Ubuntu: New Bug description: Ubuntu version: 16.04.6 Problem: in the latest release of tzdata (2019a-0ubuntu0.16.04) the entry for Asia/Novosibirsk consists of text file with the below line only: Asia/Novosibirsk Apart from not working as /etc/localtime, it also creates cryptic errors in other packages (such as PHP complaining on invalid date/time database). After I replaced the above file with the one from Ubuntu 18.04.2 tzdata's latest release, the error was gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1826968/+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 1702801] Re: Apparmor complaints about sssd_pac_plugin.so in dmesg
This still occurs with with ubuntu 19.04. This also may be a potential resource leak/security problem. It looks like each authentication creates a new entry in processe's maps file that looks like this: /usr/lib/x86_64-linux-gnu/krb5/plugins/authdata/sssd_pac_plugin.so After running for some time slapd processes gets many of those: cat /proc/877/maps | grep sssd_pac_plugin.so | wc -l 3381 I guess at some point it will run out of resources and crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1702801 Title: Apparmor complaints about sssd_pac_plugin.so in dmesg Status in openldap package in Ubuntu: New Bug description: I have slapd running and use krb authentication. Every time someone authenticates on a box connected to slapd/krb I get a few lines like this in server logs: audit: type=1400 audit(1499390102.162:5253): apparmor="DENIED" operation="file_mmap" profile="/usr/sbin/slapd" name="/usr/lib/x86_64 -linux-gnu/krb5/plugins/authdata/sssd_pac_plugin.so" pid=2513 comm="slapd" requested_mask="m" denied_mask="m" fsuid=107 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1702801/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
"1805077 do not appear again." [https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/comments/13] So let's allow this bug to expire if it does not reoccur. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Incomplete Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805077/+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 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.
1805077 do not appear again. 1826730 is a different bug exist for a very long time(few years I think). My kernel version now is: widon@widon-MS-7A69:~$ uname -a Linux widon-MS-7A69 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1826730 Title: [ASUS X555YI] audio crackle when the sound a little loud. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826730/+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 1826730] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1826730 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1826730 Title: [ASUS X555YI] audio crackle when the sound a little loud. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826730/+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 1826944] Re: green bars in ubuntu videos
Please: 1. Attach a screenshot or photo of the problem. 2. Tell us which video player apps are affected. 3. Try this: sudo apt install mpv and then use 'mpv VIDEOFILE.mp4'. Does it have the same problem? 4. Run: vainfo > vainfo.txt and send us the resulting file 'vainfo.txt'. ** Package changed: xorg (Ubuntu) => totem (Ubuntu) ** Changed in: totem (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/1826944 Title: green bars in ubuntu videos Status in totem package in Ubuntu: Incomplete Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1826944/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly
** Summary changed: - the audio pause and repeat for a very short of time randomly + [ASUS X555YI] the audio pause and repeat for a very short of time randomly -- 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/1805077 Title: [ASUS X555YI] the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: New Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805077/+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 1826730] Re: [ASUS X555YI] audio crackle when the sound a little loud.
Is this an improvement or change compared to when you reported bug 1805077 a few months ago? If this bug is only new then we should look at different kernel versions between then and now. ** Summary changed: - mp4 audio Crackle when the sound a little loud. + [ASUS X555YI] audio crackle when the sound a little loud. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1826730 Title: [ASUS X555YI] audio crackle when the sound a little loud. Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826730/+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 1826926] Re: Wallpaper bug
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 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 1809407, 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. ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend -- 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/1826926 Title: Wallpaper bug Status in xorg package in Ubuntu: New Bug description: When I close my notebook and open it subsequently the wallpaper appears "bugged". ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 15:34:24 2019 DistUpgraded: 2019-04-19 16:19:48,671 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940MX] [1025:119a] InstallationDate: Installed on 2018-12-30 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a060 Quanta Computer, Inc. Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=868f2a9b-7478-443e-a534-5d2779a0cf68 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (9 days ago) dmi.bios.date: 01/08/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd01/08/2018:svnAcer:pnAspireA515-51G:pvrV1.15:rvnKBL:rnCharmander_KL:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1826926/+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 1826943] Re: working good now.....
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed
("internal problem"). To help us find the cause of the crash please
follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** 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/1826943
Title:
working good now.
Status in Ubuntu:
Incomplete
Bug description:
slow to boot had to change wireless card to get internet.keep
getting message expirienceing internal problem have to restart?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Apr 29 17:45:32 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
bcmwl, 6.30.223.271+bdcom, 4.15.0-45-generic, i686: installed
bcmwl, 6.30.223.271+bdcom, 4.15.0-48-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Gateway, Inc. Mobile 945GM/GMS, 943/940GML Express Integrated
Graphics Controller [107b:0685]
Subsystem: Gateway, Inc. Mobile 945GM/GMS/GME, 943/940GML Express
Integrated Graphics Controller [107b:0685]
InstallationDate: Installed on 2019-04-28 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386
(20190227.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway MX8711
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic
root=UUID=e9d6bd6b-9f4a-4b07-aa2b-628b5fdc5522 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 72.11
dmi.board.vendor: Gateway
dmi.board.version: 72.11
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.version: Rev.1
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr72.11:bd11/28/2006:svnGateway:pnMX8711:pvr3408023R:rvnGateway:rn:rvr72.11:cvnGateway:ct8:cvrRev.1:
dmi.product.name: MX8711
dmi.product.version: 3408023R
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Apr 29 17:34:19 2019
xserver.configfile: default
xserver.errors:
/dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
/dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 14407
vendor SEC
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
To ma
[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1826025 Title: gnome-shell trap int3 no desktop Status in gdm3 package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking cursor. [ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955 sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8] Restarting gdm3 service results in the same trap. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell] Date: Tue Apr 23 09:56:22 2019 DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3703] InstallationDate: Installed on 2012-02-14 (2625 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Apr 22 20:53:09 2019 xserver.configfile: /home/greg/xorg.conf.new xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.4-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1826025/+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 1826947] [NEW] package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: error happens during update from ubuntu 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.12.6-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-49.53-generic 4.15.18 Uname: Linux 4.15.0-49-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 Date: Mon Apr 29 21:55:50 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-09-06 (1331 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.10 SourcePackage: fontconfig Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2019-04-29 (0 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1826947 Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: error happens during update from ubuntu 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.12.6-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-49.53-generic 4.15.18 Uname: Linux 4.15.0-49-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 Date: Mon Apr 29 21:55:50 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-09-06 (1331 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.10 SourcePackage: fontconfig Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2019-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1826947/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package zsh - 5.7.1-1ubuntu1 --- zsh (5.7.1-1ubuntu1) eoan; urgency=low * Merge from Debian unstable. Remaining changes: - debian/zshrc: Enable completions by default, unless skip_global_compinit is set. - Support cross-compiling: - Adjust upstream autoconf cross-compile default fallbacks. - Skip zcompile when cross-compiling. - Add libelf-dev dependency. * Dropped changes, included upstream: - debian/patches/CVE-2018-0502-and-CVE-2018-13259.patch: fix in Src/exec.c and add test Test/A05execution.ztst. - Cherrypick upstream patch to fix A05execution.ztst test case. Resolves autopkgtest failure. zsh (5.7.1-1) unstable; urgency=medium * [8b89d0d5,ea17cf89] New upstream bugfix release + [205859e6] Drop fix-vcs-info-p4.patch, fixed upstream [ Daniel Shahaf ] * [14d26260] d/upstream/signing-key.asc: Add the 5.7 RM's signing key. zsh (5.7-2) unstable; urgency=low [ Frank Terbeck ] * [cb6fba8] Fix perforce detection in vcs-info zsh (5.7-1) unstable; urgency=low * [9799d0f9,7b75d97c] New upstream release + Upload to unstable again. zsh (5.6.2-test-3-1) experimental; urgency=low * [325fceab,7e6a3d734] New upstream release candidate + [f64cd71d] Fixes FTBFS on 32-bits architectures * [2c01967c] debian/pkg-zsh-workflow-new-upstream-release.md fine-tuning * [30825099] Bump debhelper compatibility level to 12. + Use b-d on "debhelper-compat (= 12)" instead of debian/compat. * [087d6045] Change shebang path in example script to Debian's zsh path. * [6cbe67e6] Make autopkgtest pass by including config.modules in zsh-dev. (Test/V07pcre.ztst now tries to access ../config.modules to check if the PCRE module was enabled and needs to be tested. The test emits a warning on STDERR if ../config.modules is not found.) zsh (5.6.2-test-2-1) experimental; urgency=low * [9dbde9e,bf8b7f7] New upstream release candidate + [dc2bfeee] Have V07pcre fail if PCRE was enabled by configure (config.modules) but failed to load for any reason. (Closes: #909114) + [44b0a973] Remove all cherry-picked patches. + [01c3153e] debian/rules: Build zshbuiltins.1 out-of-tree like the rest. [ Daniel Shahaf ] * [19fed9e6] debian/upstream/signing-key.asc: Add the upstream signing key used since 5.5.1-test-1. [ Ondřej Nový ] * [b402fc2e] debian/tests: Use AUTOPKGTEST_TMP instead of ADTTMP. [ Axel Beckert ] * [24256bb7] Add zsh-autosuggestions to list of zsh-related packages in bug-script. * [1239bb28] Declare compliance with Debian Policy 4.3.0. (No other changes were necessary.) * [06946d43] debian/TODO.md: Mention that switching zsh-dev to arch:all is non-trivial. * [e0798c2f] Declare debian/pkg-zsh-workflow.md as outdated. Add debian/pkg-zsh-workflow-new-upstream-release.md as massively reduced replacement. zsh (5.6.2-3) unstable; urgency=medium * [92175749] Revert "Switch from the deprecated libpcre3 to the newer (!) libpcre2." libpcre2 is not a drop-in replacement and not detected by zsh's configure script. (Closes: #909084, reopens LP#1792544) zsh (5.6.2-2) unstable; urgency=medium [ Axel Beckert ] * [a5db2473] Switch from the deprecated libpcre3 to the newer (!) libpcre2. (LP: #1792544) [ Daniel Shahaf ] * [3d8f4eee] Cherry-pick 551ff842 from upstream: Another attachtty() fix. (Closes: #908818) zsh (5.6.2-1) unstable; urgency=medium * [92bef885,3d116bbb] New upstream bugfix release. + [490c395d] Refresh further-mitigate-test-suite-hangs.patch. + [7c5241ed] 43446: More entersubsh() / addproc() wiring. (Closes: #908033, #908818) + [07ad7fd9] Fix windowsize when reattaching to terminal on process exit. (Closes: #908625) [ Daniel Shahaf ] * [77265d89] d/README.Debian: Fix typo. [ Axel Beckert ] * [5484e5d4] Cherry-pick decc78c72 from upstream: _svn: Allow hyphens in command name aliases. zsh (5.6.1-1) unstable; urgency=medium * [b3239c5e,b531f38d] New upstream bugfix release. + [0d5275c6] Fix process group setting in main shell. (Mitigates: #908033) * [5379b4c6] Retroactively mention #908000 in previous changelog entry. * [a04e81b6] Update README.Debian wrt. -dbg vs -dbgsym packages and apt-get vs apt. zsh (5.6-1) unstable; urgency=high * [b30b8941,6e6500bfa] New upstream release. + [ec2144bb] Refresh patch further-mitigate-test-suite-hangs.patch. + [1c4c7b6a] Fixes two security issues in shebang line parsing. (CVE-2018-0502, CVE-2018-13259; Closes: #908000) + Upload to unstable with high urgency. * [c605c9a1] Install symlinks to NEWS.gz (Policy 4.2.0) + README.Debian to /usr/share/doc/zsh/. Drop no more used symlink from changelog.gz to ../zsh-common/changelog.gz from debian/zsh.links. Update debian/TODO.md with some minor, but non-trivial documentation issues recently noticed. zsh (5.5.1-test-2-
[Touch-packages] [Bug 1826944] [NEW] green bars in ubuntu videos
Public bug reported: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1826944 Title: green bars in ubuntu videos Status in xorg package in Ubuntu: New Bug description: When I try to play a .mp4 video in Ubuntu Video, I get a screen with green bars all over. The problem does not occur when I switch to my nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:02:44 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:1590] InstallationDate: Installed on 2019-04-28 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. GL753VE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL753VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK
[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab
I should note this is impacting an image built from 16.04.4. Another image built from 16.04.1 is working fine. Both have been pulled forward via apt dist-upgrade and their behaviors differ - concerning in it's own right. -- 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/1577575 Title: NFS share does not mount on boot using fstab Status in nfs-utils package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1826943] [NEW] working good now.....
Public bug reported: slow to boot had to change wireless card to get internet.keep getting message expirienceing internal problem have to restart? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 29 17:45:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-45-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-48-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gateway, Inc. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [107b:0685] Subsystem: Gateway, Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [107b:0685] InstallationDate: Installed on 2019-04-28 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gateway MX8711 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=e9d6bd6b-9f4a-4b07-aa2b-628b5fdc5522 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 72.11 dmi.board.vendor: Gateway dmi.board.version: 72.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: Rev.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr72.11:bd11/28/2006:svnGateway:pnMX8711:pvr3408023R:rvnGateway:rn:rvr72.11:cvnGateway:ct8:cvrRev.1: dmi.product.name: MX8711 dmi.product.version: 3408023R dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 29 17:34:19 2019 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14407 vendor SEC xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1826943 Title: working good now. Status in xorg package in Ubuntu: New Bug description: slow to boot had to change wireless card to get internet.keep getting message expirienceing internal problem have to restart? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 29 17:45:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-45-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-48-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corpora
[Touch-packages] [Bug 1788048] Re: systemd journald failed unmounting var
** Changed in: systemd 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/1788048 Title: systemd journald failed unmounting var Status in systemd: New Status in systemd package in Ubuntu: Triaged Bug description: When the system is shut down or restarted the systemd-journal does not disassemble the disks correctly. On this thread https://unix.stackexchange.com/questions/378678/why- do-i-get-the-error-failed-unmounting-var-during-shutdown I checked what editing /etc/systemd/journald.conf to change the Storage = line to Storage = volatile the problem is solved, but some of the logs on the shutdown are lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 20 18:15:07 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-08-20 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1788048/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
** Changed in: systemd 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 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/systemd/+bug/1773148/+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 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales
Probably related:
https://bugzilla.redhat.com/show_bug.cgi?id=1336308
and probably related:
https://sourceware.org/git/?p=glibc.git;a=commit;h=b11643c21c5c9d67a69c8ae952e5231ce002e7f1
Thanks
** Bug watch added: Red Hat Bugzilla #1336308
https://bugzilla.redhat.com/show_bug.cgi?id=1336308
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1774857
Title:
sort doesn't sort and uniq loses data for many non-Latin scripts on
UTF-8 locales
Status in coreutils package in Ubuntu:
New
Status in glibc package in Ubuntu:
New
Bug description:
I’ve found out that sort doesn’t sort strings for many non-Latin
scripts at all if the locale you’re using is one of en_US.UTF-8,
fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
expected. Here’s a test case:
Open xterm, launch sort and input some lines of Syriac, Ethiopic,
Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
repeating one of the lines twice. Here’s an example in Syriac:
ܡܠܬܐ
ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ
Sort produces the following:
ܡܠܬܐ
ܒܝܬܐ
ܡܠܬܐ
ܒܪܢܫܐ
Here strings are ordered only according to their length but not
characters. Even the two instances of the word ܡܠܬܐ are found on non-
adjacent lines (1 and 3). The expected sort order based on Unicode
points would be:
ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ
ܡܠܬܐ
If you further pass sort’s output to uniq, it produces the following:
ܡܠܬܐ
ܒܪܢܫܐ
Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
seems to consider all Syriac strings of equal length as the same.
Although this issue affects locale, I think it is not a locale issue
per se, since perl seems to handle similar cases expectedly. For
instance, the following command produces the expected result:
perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
"ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'
Curiously enough, codepoints in Plane 1 seem to count as two
codepoints of the basic plane, so that if you sort | uniq the
following (six codepoints of Syriac and three codepoints of
Phoenician):
ܥܠܝܟܘܢ
𐤁𐤉𐤕
you get ”ܥܠܝܟܘܢ" as the result whereas ”𐤁𐤉𐤕” is lost. This is of
course due to the UTF-8 representation of Plane 1 characters as two
surrogate characters on the basic plane.
Also curiously, LTR scripts seem to conflate with each other and RTL
scripts among themselves but not across the directionality line, so
that if you sort | uniq the following (three codepoints each in
Ethiopic, Hangul, Syriac, Hiragana and Thai):
ዘመን
스물셋
ܐܢܐ
わたし
ฟ้า
you are left with:
ܐܢܐ
ዘመን
That’s one line of Syriac and one line of Ethiopic; everything else
was lost. This issue does not seem to affect most Indic scripts
(Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
expected for the main Unicode block (4E00..9FFF) but not for Extension
A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
to αὐλῆς). For Hebrew, letters and vowel marks work fine but
cantillation marks are conflated.
Description: Ubuntu 18.04 LTS
Release: 18.04
coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
*** 8.28-1ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: coreutils 8.28-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 3 10:13:06 2018
InstallationDate: Installed on 2017-02-13 (474 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fi_FI.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1774857/+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 1826939] [NEW] Network restart after suspend is unreliable
Public bug reported: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. >From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 11:16:05 CEST; 12h ago Docs: man:interfaces(5) Main PID: 1239 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/networking.service Apr 29 11:15:58 gonzales systemd[1]: Starting Raise network interfaces... Apr 29 11:15:59 gonzales ifup[1239]: ifup: waiting for lock on /run/network/ifstate.eno1 Apr 29 11:16:05 gonzales systemd[1]: Started Raise network interfaces. After I have done a "sudo service networking restart", the output is this: klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 23:17:00 CEST; 5s ago Docs: man:interfaces(5) Process: 3701 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Main PID: 3701 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) Memory: 7.4M CGroup: /system.slice/networking.service └─3728 /sbin/dhclient -1 -4 -v -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df /var/lib/dhcp/dhclient6.eno1.leases eno1 Apr 29 23:16:59 gonzales ifup[3701]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x53439c24) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales dhclient[3728]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales ifup[3701]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales ifup[3701]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:16:59 gonzales ifup[3701]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:17:00 gonzales dhclient[3728]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales ifup[3701]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales systemd[1]: Started Raise network interfaces. (And the pings work fine again, too.) This is a regression after the upgrade from 18.10 (where networking wakeup worked fine) to 19.04. Version info: klee@gonzales:~$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 netbase 5.6 ifupdown 0.8.34ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: netbase 5.6 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 29 23:19:00 2019 Dependencies: InstallationDate: Installed on 2016-08-06 (996 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: netbase UpgradeStatus: Upgraded to disco on 2019-04-21 (8 days ago) ** Affects: netbase (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 netbase in Ubuntu. https://bugs.launchpad.net/bugs/1826939 Title: Network restart after suspend is unreliable Status in netbase package in Ubuntu: New Bug description: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonza
[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab
Same issue here. NFS fails to mount at boot, but logging in and issuing a manual "mount -a" resolves until the next reboot. It should also be noted that there's a significant delay on boot with nfs entries in fstab - need to time it, but ~1 minute. Why issues with something as old/stable/boring as NFS? ** Also affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab Status in nfs-utils package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1826931] Re: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:am
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1826931 Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 Status in mesa package in Ubuntu: New Bug description: I was doing do-release-upgrade from terminal but somehow the process stopped. I'm stuck on 18.10 and when I do do-release-upgrade it wants me to update all packages before distro upgrading. It tries to download packages from the 19.04 repo ProblemType: Package DistroRelease: Ubuntu 19.04 Package: mesa-common-dev 19.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompositorRunning: None Date: Mon Apr 29 22:28:32 2019 DistUpgraded: 2019-04-29 22:18:48,041 DEBUG inhibit gnome-session idle DistroCodename: disco DistroVariant: ubuntu DuplicateSignature: package:mesa-common-dev:19.0.2-1ubuntu1 Unpacking mesa-common-dev:amd64 (19.0.2-1ubuntu1) over (19.0.1-0~c~padoka0) ... dpkg: error processing archive /tmp/apt-dpkg-install-eeRqan/097-mesa-common-dev_19.0.2-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 ErrorMessage: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake GT2 [HD Graphics 520] [1558:2425] InstallationDate: Installed on 2019-03-13 (46 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b551 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N24_25JU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=7e8a7184-5a6a-41bd-8f32-b0efd253c9d1 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.7.4 SourcePackage: mesa Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 UpgradeStatus: Upgraded to disco on 2019-04-29 (0 days ago) dmi.bios.date: 03/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/31/2016:svnPCSpecialistLimited:pnN24_25JU:pvrNotApplicable:rvnCLEVO:rnN24_25JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1826931/+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 1826931] [NEW] package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:
Public bug reported: I was doing do-release-upgrade from terminal but somehow the process stopped. I'm stuck on 18.10 and when I do do-release-upgrade it wants me to update all packages before distro upgrading. It tries to download packages from the 19.04 repo ProblemType: Package DistroRelease: Ubuntu 19.04 Package: mesa-common-dev 19.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompositorRunning: None Date: Mon Apr 29 22:28:32 2019 DistUpgraded: 2019-04-29 22:18:48,041 DEBUG inhibit gnome-session idle DistroCodename: disco DistroVariant: ubuntu DuplicateSignature: package:mesa-common-dev:19.0.2-1ubuntu1 Unpacking mesa-common-dev:amd64 (19.0.2-1ubuntu1) over (19.0.1-0~c~padoka0) ... dpkg: error processing archive /tmp/apt-dpkg-install-eeRqan/097-mesa-common-dev_19.0.2-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 ErrorMessage: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake GT2 [HD Graphics 520] [1558:2425] InstallationDate: Installed on 2019-03-13 (46 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b551 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N24_25JU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=7e8a7184-5a6a-41bd-8f32-b0efd253c9d1 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.7.4 SourcePackage: mesa Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 UpgradeStatus: Upgraded to disco on 2019-04-29 (0 days ago) dmi.bios.date: 03/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/31/2016:svnPCSpecialistLimited:pnN24_25JU:pvrNotApplicable:rvnCLEVO:rnN24_25JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 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: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco package-conflict ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1826931 Title: package mesa-common-dev 19.0.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/KHR/khrplatform.h', which is also in package libegl1-mesa-dev:amd64 19.0.1-0~c~padoka0 Status in mesa package in Ubuntu: New Bug description: I was doing do-release-upgrade from terminal but somehow the process stopped. I'm stuck on 18.10 and when I do do-release-upgrade it wants me to update all packages before distro upgrading. It tries to download packages from the 19.04 repo ProblemType: Package DistroRelease: Ubuntu 19.04 Package: mesa-common-dev 19.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompositorRunning: None Date: Mon Apr 29 22:28:32 2019 DistUpgraded: 2019-04-29 22:18:48,041 DEBUG inhibit gnome-session idle DistroCodename: disco DistroVariant: ubuntu DuplicateSignature: package:mesa-common-dev:19.0.2-1
[Touch-packages] [Bug 1826735] Re: .uuid files in font directories not removed during purge
** Changed in: fontconfig (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1826735 Title: .uuid files in font directories not removed during purge Status in fontconfig package in Ubuntu: New Status in fontconfig package in Debian: Confirmed Bug description: On Ubuntu 19.04 (amd64): Removing fonts-liberation2 (2.00.5-1) ... dpkg: warning: while removing fonts-liberation2, directory '/usr/share/fonts/truetype/liberation2' not empty so not removed Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ... dpkg: warning: while removing fonts-opensymbol, directory '/usr/share/fonts/truetype/openoffice' not empty so not removed ls -a against these directories shows there's still .uuid files in there which dpkg -S is unaware of. Upstream bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=897040 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1826735/+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 1822717] Update Released
The verification of the Stable Release Update for binutils 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1822717 Title: SRU: build more cross packages on arm64 and ppc64el Status in binutils package in Ubuntu: New Status in binutils source package in Bionic: Fix Released Status in binutils source package in Cosmic: Fix Released Bug description: extending LP: #1769657, this builds more cross packages on arm64 and ppc64el: * Build ppc64el packages on arm64. * Build s390x packages on arm64 and ppc64el. * Build riscv64 packages on arm64 and ppc64el. SRU information: This is a no-change upload for all existing binary packages, it just add some more new cross packages. Regression potential is the same as for any other no-change upload. Test case: make sure the selected new cross packages build on the newly enabled architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1822717/+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 1822717] Re: SRU: build more cross packages on arm64 and ppc64el
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04.1 --- binutils (2.30-21ubuntu1~18.04.1) bionic-proposed; urgency=medium * SRU: LP: #1822717. * Build ppc64el packages on arm64. * Build s390x packages on arm64 and ppc64el. * Build riscv64 packages on arm64 and ppc64el. -- Matthias Klose Tue, 02 Apr 2019 07:12:48 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1822717 Title: SRU: build more cross packages on arm64 and ppc64el Status in binutils package in Ubuntu: New Status in binutils source package in Bionic: Fix Released Status in binutils source package in Cosmic: Fix Released Bug description: extending LP: #1769657, this builds more cross packages on arm64 and ppc64el: * Build ppc64el packages on arm64. * Build s390x packages on arm64 and ppc64el. * Build riscv64 packages on arm64 and ppc64el. SRU information: This is a no-change upload for all existing binary packages, it just add some more new cross packages. Regression potential is the same as for any other no-change upload. Test case: make sure the selected new cross packages build on the newly enabled architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1822717/+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 1822717] Re: SRU: build more cross packages on arm64 and ppc64el
This bug was fixed in the package binutils - 2.31.1-6ubuntu1.1 --- binutils (2.31.1-6ubuntu1.1) cosmic-proposed; urgency=medium * SRU: LP: #1822717. * Build ppc64el packages on arm64. * Build s390x packages on arm64 and ppc64el. * Build riscv64 packages on arm64 and ppc64el. -- Matthias Klose Tue, 02 Apr 2019 08:11:16 +0200 ** Changed in: binutils (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: binutils (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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1822717 Title: SRU: build more cross packages on arm64 and ppc64el Status in binutils package in Ubuntu: New Status in binutils source package in Bionic: Fix Released Status in binutils source package in Cosmic: Fix Released Bug description: extending LP: #1769657, this builds more cross packages on arm64 and ppc64el: * Build ppc64el packages on arm64. * Build s390x packages on arm64 and ppc64el. * Build riscv64 packages on arm64 and ppc64el. SRU information: This is a no-change upload for all existing binary packages, it just add some more new cross packages. Regression potential is the same as for any other no-change upload. Test case: make sure the selected new cross packages build on the newly enabled architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1822717/+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 1824341] Re: NoAllowedOrigin cause package removal
** Description changed: + [Impact] + + * When applying a minimal upgrade set fails raising an exception + unattended-upgrades stops trying to install further sets and may remove + packages left marked to remove in the dirty set. + + [Test Case] + + * Set up unattended-upgrades to always remove autoremovable packages: + +$ echo 'Unattended-Upgrade::Remove-Unused-Dependencies "false";' | sudo tee /etc/apt/apt.conf.d/51unattended-upgrades-remove + * Install a package and mark it as autoremovable + +$ sudo apt install hello +$ sudo apt-mark auto hello + + * Set up the custom package to trigger the failure with the exception when applying the minimal sets in a way that leaves packages to remove in the dirty cache. If the reporter can reproduce the issue on all releases then that's great, otherwise I provide an example with equivs. + + * Check if u-u still crashes + $ sudo unattended-upgrades -d + + [Regression Potential] + + * The fix is catching the raised exceptions and trying to apply next minimal sets. In special circumstances this could fail again for all sets or could make systems's state worse if the installation is already broken. I can't come up with an example where it would make the system's state worse because when packages can't be safely installed Cache.commit() is expected to fail earlier, thust making the system's state worse seems unlikely. + * OTOH when upgrading a set fails this would not block the installation of bigger sets anymore which is a big advantage of having this fix in u-u. + + [Original Bug Text] + unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log that happens package removal: $ sudo unattended-upgrade -d [...] Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 257, in call_adjusted - self.allowed_origins) - File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin - raise NoAllowedOriginError() + File "/usr/bin/unattended-upgrade", line 257, in call_adjusted + self.allowed_origins) + File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin + raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True - Exception: + Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common marking cliente-ldap for removal (Reading database ... 213413 files and directories currently installed.) Removing cliente-ldap (1:2.17.15) ... marking libcephfs2 for removal (Reading database ... 213392 files and directories currently installed.) Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking ldap-auth-config for removal (Reading database ... 213386 files and directories currently installed.) Removing libpam-ldap:amd64 (186-4ubuntu1) ... Removing ldap-auth-config (0.5.3) ... Removing ldap-auth-client (0.5.3) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking python-samba for removal (Reading database ... 213332 files and directories currently installed.) Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking nss-updatedb for removal (Reading database ... 212865 files and directories currently installed.) Removing nss-updatedb (10-3build1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-vfs-modules for removal (Reading database ... 212859 files and directories currently installed.) Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ub
[Touch-packages] [Bug 1826926] [NEW] Wallpaper bug
Public bug reported: When I close my notebook and open it subsequently the wallpaper appears "bugged". ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 15:34:24 2019 DistUpgraded: 2019-04-19 16:19:48,671 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940MX] [1025:119a] InstallationDate: Installed on 2018-12-30 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a060 Quanta Computer, Inc. Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=868f2a9b-7478-443e-a534-5d2779a0cf68 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (9 days ago) dmi.bios.date: 01/08/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd01/08/2018:svnAcer:pnAspireA515-51G:pvrV1.15:rvnKBL:rnCharmander_KL:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu ** Attachment added: "My original wallpaper is 80s disco dingo from ubuntu 19.04" https://bugs.launchpad.net/bugs/1826926/+attachment/5260028/+files/Captura%20de%20tela%20de%202019-04-29%2015-27-33.png -- 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/1826926 Title: Wallpaper bug Status in xorg package in Ubuntu: New Bug description: When I close my notebook and open it subsequently the wallpaper appears "bugged". ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 15:34:24 2019 DistUpgraded: 2019-04-19 16:19:48,671 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: disco DistroVariant: u
[Touch-packages] [Bug 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
This bug was fixed in the package python-stdlib-extensions - 2.7.16-2~18.10 --- python-stdlib-extensions (2.7.16-2~18.10) cosmic-proposed; urgency=medium * SRU: LP: #1822993. python-stdlib-extensions (2.7.16-2) unstable; urgency=medium * Re-pack the orig tarball without the VCS repo. python-stdlib-extensions (2.7.16-1) unstable; urgency=medium * Python 2.7.16 release. python-stdlib-extensions (2.7.16~rc1-1) unstable; urgency=medium * Python 2.7.16 release candidate. * Bump standards version. * Fix FTCBFS (Helmut Grohne). Closes: #913417. + Multiarchify Build-Depends. + Set up PYTHONPATH for cross compilation. + cross.patch: Don't import built modules. -- Matthias Klose Tue, 09 Apr 2019 06:54:11 +0200 ** Changed in: python-stdlib-extensions (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Released Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1826902] [NEW] /usr/sbin/usbmuxd:free(): invalid pointer
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding usbmuxd. This problem was most recently seen with package version 1.1.0-2ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/0ab3146f9a13cc10682e6a4210ead867d649869f 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: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1826902 Title: /usr/sbin/usbmuxd:free(): invalid pointer Status in usbmuxd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding usbmuxd. This problem was most recently seen with package version 1.1.0-2ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/0ab3146f9a13cc10682e6a4210ead867d649869f 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/usbmuxd/+bug/1826902/+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 1808476] Re: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants
This bug was fixed in the package python2.7 - 2.7.16-2~18.10 --- python2.7 (2.7.16-2~18.10) cosmic-proposed; urgency=medium * SRU: LP: #1822993. python2.7 (2.7.16-2) unstable; urgency=high [ Matthias Klose ] * CVE-2019-9636. Fix issue #36216: Add check for characters in netloc that normalize to separators. Closes: #924073. * CVE-2019-9948. Fix issue #35907: Stop urllib exposing the local_file schema (file://). [ Dimitri John Ledkov ] * Bump Build-Depedency and Dependency of libssl-dev and libss1.1 to 1.1.1 or higher. As TLS1.3 constants leak into ssl module, thus one shouldn't mix and match python2.7 & libssl1.1. LP: #1808476 python2.7 (2.7.16-1) unstable; urgency=medium * Python 2.7.16 release. - Now has a version without a trailing '+'. Closes: #914072. python2.7 (2.7.16~rc1-1) unstable; urgency=medium * Python 2.7.16 release candidate 1. python2.7 (2.7.15-9) unstable; urgency=medium * Update to 20190216 from the 2.7 branch. - Backport of TLS 1.3 related fixes from 3.7. * Drop the local TLS 1.3 backports. python2.7 (2.7.15-8) unstable; urgency=medium * Fix typo in autopkg test. python2.7 (2.7.15-7) unstable; urgency=medium * Expect the test_site test failing as in 3.7. python2.7 (2.7.15-6) unstable; urgency=medium * Update to 20190201 from the 2.7 branch. - CVE-2013-1752: Limit imaplib.IMAP4_SSL.readline(). - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt(). Closes: #921039. - CVE-2019-5010: DsO vulnerability exists in the X509 certificate parser. Closes: #921040. * Bump standards version. * Update symbols file. python2.7 (2.7.15-5) unstable; urgency=medium * Update to 20181127 from the 2.7 branch. - Fix issue #20744, running an external 'zip' in shutil.make_archive(). CVE-2018-1000802. Closes: #909673. * Cherrypick in-progress backports to 2.7 branch from 3.6 branch to fix test_ssl assertions with openssl 1.1.1. Resolves autopkgtest failure of the 2.7 with openssl 1.1.1 (Dimitri John Ledkov). * Don't hard code location of netinet/in.h. Closes: #912422. * Update VCS attributes. -- Matthias Klose Tue, 09 Apr 2019 06:50:39 +0200 ** Changed in: python2.7 (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-1752 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2018-1000802 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14647 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5010 -- 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/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Bionic: New Status in python2.7 source package in Cosmic: Fix Released Status in python2.7 source package in Disco: Fix Released Bug description: [Impact] $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. [Test Case] Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. [Regression Potential] Potentially none, besides the usual regression potential of new rebuilds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+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 1822993] Update Released
The verification of the Stable Release Update for python3.6 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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
This bug was fixed in the package python3-stdlib-extensions - 3.6.8-1~18.10 --- python3-stdlib-extensions (3.6.8-1~18.10) cosmic-proposed; urgency=medium * SRU: LP: #1822993. * Update 3.6 extensions and modules to 3.6.8. * Update 3.7 extensions and modules to 3.7.3. -- Matthias Klose Tue, 09 Apr 2019 07:04:33 +0200 -- 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/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
This bug was fixed in the package python2.7 - 2.7.16-2~18.10 --- python2.7 (2.7.16-2~18.10) cosmic-proposed; urgency=medium * SRU: LP: #1822993. python2.7 (2.7.16-2) unstable; urgency=high [ Matthias Klose ] * CVE-2019-9636. Fix issue #36216: Add check for characters in netloc that normalize to separators. Closes: #924073. * CVE-2019-9948. Fix issue #35907: Stop urllib exposing the local_file schema (file://). [ Dimitri John Ledkov ] * Bump Build-Depedency and Dependency of libssl-dev and libss1.1 to 1.1.1 or higher. As TLS1.3 constants leak into ssl module, thus one shouldn't mix and match python2.7 & libssl1.1. LP: #1808476 python2.7 (2.7.16-1) unstable; urgency=medium * Python 2.7.16 release. - Now has a version without a trailing '+'. Closes: #914072. python2.7 (2.7.16~rc1-1) unstable; urgency=medium * Python 2.7.16 release candidate 1. python2.7 (2.7.15-9) unstable; urgency=medium * Update to 20190216 from the 2.7 branch. - Backport of TLS 1.3 related fixes from 3.7. * Drop the local TLS 1.3 backports. python2.7 (2.7.15-8) unstable; urgency=medium * Fix typo in autopkg test. python2.7 (2.7.15-7) unstable; urgency=medium * Expect the test_site test failing as in 3.7. python2.7 (2.7.15-6) unstable; urgency=medium * Update to 20190201 from the 2.7 branch. - CVE-2013-1752: Limit imaplib.IMAP4_SSL.readline(). - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt(). Closes: #921039. - CVE-2019-5010: DsO vulnerability exists in the X509 certificate parser. Closes: #921040. * Bump standards version. * Update symbols file. python2.7 (2.7.15-5) unstable; urgency=medium * Update to 20181127 from the 2.7 branch. - Fix issue #20744, running an external 'zip' in shutil.make_archive(). CVE-2018-1000802. Closes: #909673. * Cherrypick in-progress backports to 2.7 branch from 3.6 branch to fix test_ssl assertions with openssl 1.1.1. Resolves autopkgtest failure of the 2.7 with openssl 1.1.1 (Dimitri John Ledkov). * Don't hard code location of netinet/in.h. Closes: #912422. * Update VCS attributes. -- Matthias Klose Tue, 09 Apr 2019 06:50:39 +0200 ** Changed in: python3-stdlib-extensions (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
This bug was fixed in the package python3.7 - 3.7.3-2~18.10
---
python3.7 (3.7.3-2~18.10) cosmic; urgency=medium
* SRU: LP: #1822993. Update to the 3.7.3 release.
python3.7 (3.7.3-2) unstable; urgency=medium
* d/p/arm-alignment.diff: Don't allow unaligned memory accesses in the
_sha3 extension (Dave Jones). LP: #1821869. Issue #36515.
* Tweak the asyncio/ssl test again.
python3.7 (3.7.3-1) unstable; urgency=medium
* Python 3.7.3 release.
* Work around issue #35988, reducing the payload size for the asyncio/ssl
tests.
python3.7 (3.7.3~rc1-1) unstable; urgency=medium
* Python 3.7.3 release candidate 1.
* CVE-2019-9636. Fix issue #36216: Add check for characters in netloc that
normalize to separators. Closes: #924072.
* Use a build profile for libbluetooth-dev ().
python3.7 (3.7.2-3) unstable; urgency=medium
* Update to 20190227 from the 3.7 branch.
* Add more breaks for packages not compatible with Python 3.7:
- xapers. Closes: #916914.
* Move the test/ann_module{,2,3} modules into libpython-stdlib.
Closes: #922285.
* Limit the import checks for some extension modules to native builds.
Closes: #921742.
python3.7 (3.7.2-2) unstable; urgency=medium
* Update to 20190202 from the 3.7 branch.
python3.7 (3.7.2-1) unstable; urgency=medium
* Python 3.7.2 release.
* Revert the link optimization changes which appeared after the
release candidate.
* Make the build compatible with sphinx 1.6.x.
* Loosen the pyzo break. Closes: #916548.
python3.7 (3.7.2~rc1-1) unstable; urgency=medium
* Python 3.7.2 release candidate 1.
* Add more breaks for packages not compatible with Python 3.7:
- python3-dns. Closes: #912988.
- python3-dkim. Closes: #912084.
- pyzo. Closes: #914332.
* Update VCS attributes. Closes: #904097.
* Update symbols files.
-- Matthias Klose Tue, 09 Apr 2019 06:56:51 +0200
** Changed in: python2.7 (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-1752
** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-1000802
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14647
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5010
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9948
--
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/1822993
Title:
SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
Status in python-stdlib-extensions package in Ubuntu:
Fix Released
Status in python2.7 package in Ubuntu:
Fix Released
Status in python3-stdlib-extensions package in Ubuntu:
Fix Released
Status in python3.7 package in Ubuntu:
Fix Released
Status in python-stdlib-extensions source package in Bionic:
Fix Committed
Status in python3-stdlib-extensions source package in Bionic:
Fix Committed
Status in python-stdlib-extensions source package in Cosmic:
Fix Committed
Status in python2.7 source package in Cosmic:
Fix Released
Status in python3-stdlib-extensions source package in Cosmic:
Fix Released
Status in python3.6 source package in Cosmic:
Fix Released
Status in python3.7 source package in Cosmic:
Fix Released
Bug description:
SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the
3.6.8 release.
python3-stdlib-extensions also updates the modules to the 3.6.8
release for Python 3.6.
Acceptance Criteria: The package builds, and the test suite doesn't
show regressions. The test suite passes in the autopkg tests. The new
packages don't cause regressions in a test rebuild of the main
component.
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html
The test rebuilds are finished, and don't show any regressions for the
main component.
Regression Potential: Python 3.7 isn't used by default, so we don't have many
default users.
Regression Potential: Python 3.6 could see some regressions, although we are
trying to minimize the risk by doing the test rebuild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
This bug was fixed in the package python3.6 - 3.6.8-1~18.10 --- python3.6 (3.6.8-1~18.10) cosmic-proposed; urgency=medium * PPA upload. * SRU: LP: #1822993. Update to the 3.6.8 release. * d/p/arm-alignment.diff: Don't allow unaligned memory accesses in the _sha3 extension (Dave Jones). LP: #1821869. Issue #36515. python3.6 (3.6.8-1) unstable; urgency=medium * Python 3.6.8 release. * Revert the link optimization changes which appeared after the release candidate. python3.6 (3.6.8~rc1-1) unstable; urgency=medium * Python 3.6.8 release candidate 1. * Update symbols files. -- Matthias Klose Tue, 09 Apr 2019 06:59:38 +0200 ** Changed in: python3.6 (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: python3.7 (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9636 -- 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/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
I checked those and hinted them for cosmic. This looks now good to release. -- 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/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python3-stdlib-extensions source package in Cosmic: Fix Released Status in python3.6 source package in Cosmic: Fix Released Status in python3.7 source package in Cosmic: Fix Released Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1822270] Re: Debconf readline frontend does not show options
** Changed in: debconf (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Confirmed Status in debconf source package in Xenial: Confirmed Status in debconf source package in Bionic: Confirmed Status in debconf source package in Cosmic: Confirmed Status in debconf source package in Disco: Confirmed Status in debconf source package in Eoan: Confirmed Status in debconf package in Debian: New Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1816547] Re: SRU 2.56.4 to bionic
Thanks, I retried them all and AFAICS they're all going to go green now (three are red at the minute but I looked at the output on the controller). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] New upstream bug fix microrelease * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Test various parts of the desktop. - Logging in - Shutting down - Starting a variety of apps and checking that they work + rhythmbox (play a song using gstreamer) + cheese (look at yourself with your webcam using gstreamer) + network-manager + epiphany (web stuff works) Monitor the error tracker for any increases. [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1824876] Re: unattended-upgrades: call_adjusted() raises NoAllowedOriginError when marking packages to upgrade/install fails
** Description changed: + [Impact] + + * Unattended-upgrades may when it can't find a solution for installing a package when all the candidates are from not allowed origins. + * The fix is just not marking those packages to install without raising an error. + + [Test Case] + + * Observe the error not being reported against fixed versions. + + [Regression Potential] + + * The fix is not raising the error, but marking no package to install. + As a regression u-u may miss some unupgradable packages, but in the + callers this case is already handled. + + [Original Bug Text] + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu3, the problem page at https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655 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/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824876 Title: unattended-upgrades: call_adjusted() raises NoAllowedOriginError when marking packages to upgrade/install fails Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Unattended-upgrades may when it can't find a solution for installing a package when all the candidates are from not allowed origins. * The fix is just not marking those packages to install without raising an error. [Test Case] * Observe the error not being reported against fixed versions. [Regression Potential] * The fix is not raising the error, but marking no package to install. As a regression u-u may miss some unupgradable packages, but in the callers this case is already handled. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu3, the problem page at https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655 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/unattended-upgrades/+bug/1824876/+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 1824876] Re: unattended-upgrades: call_adjusted() raises NoAllowedOriginError when marking packages to upgrade/install fails
** Summary changed: - /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted + unattended-upgrades: call_adjusted() raises NoAllowedOriginError when marking packages to upgrade/install fails -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824876 Title: unattended-upgrades: call_adjusted() raises NoAllowedOriginError when marking packages to upgrade/install fails Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * Unattended-upgrades may when it can't find a solution for installing a package when all the candidates are from not allowed origins. * The fix is just not marking those packages to install without raising an error. [Test Case] * Observe the error not being reported against fixed versions. [Regression Potential] * The fix is not raising the error, but marking no package to install. As a regression u-u may miss some unupgradable packages, but in the callers this case is already handled. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu3, the problem page at https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655 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/unattended-upgrades/+bug/1824876/+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 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
The disco packages are now successfully built. All autopkg tests except for ironic, murano and murano-agent pass. These are no regressions, related to Python 3.7, and according to Corey: "If you are ok with it I don't think there's much priority in fixing these. They appear to be Python3.7 issues that are fixed in disco". If that's ok, we are good for cosmic-updates. The bionic updates are still stalled by the OpenSSL updates. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Committed Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+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 1826126] Re: ubuntu-bug fails to attach apport file
The documentation was incorrect and I've fixed it. Thanks! ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1826126 Title: ubuntu-bug fails to attach apport file Status in apport package in Ubuntu: Invalid Bug description: https://help.ubuntu.com/community/ReportingBugs reports that ``` If this is to be added to an existing bug report, also use the -u option: ubuntu-bug -c FILENAME.apport -u BUGNUMBER Please do not attach the .apport or .crash file to the report, as this is not the same as performing the above mentioned steps. ``` However, I fail to do this: ``` $ ubuntu-bug -c cartsheel.apport -u 1826125 Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] ubuntu-bug: error: -u/--update-bug option cannot be used together with options for a new report ``` This is either a ubuntu-bug or a documentation bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1826126/+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 1826311] Re: Cannot Login to Google with Advanced Protection Enabled
** Changed in: gnome-online-accounts Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1826311 Title: Cannot Login to Google with Advanced Protection Enabled Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Description: Ubuntu 19.04 Release: 19.04 gnome-online-accounts: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 1) Open Online accounts and select google (From settings or during OS setup) 2) enter username and password. What I expect: I get the prompt to plug-in my 2 factor hardware key What actually happens: I get a prompt saying, "You can only use your Security keys with Google Chrome" Not sure if this is actually fixable, I know desktop firefox has hidden settings to allow u2f, but not sure if that extends to the embedded browsers (if gnome-online-accounts even uses an embedded firefox for its browser) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 00:16:27 2019 InstallationDate: Installed on 2019-04-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1826311/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
ubuntu@fili:~$ dpkg -l |grep ureadahead ii ureadahead0.100.0-19 amd64Read required files in advance ubuntu@fili:~$ journalctl -b | grep ureadahead | wc -l 4051 (upgraded ureadhead version to -proposed, removed /var/lib/ureadahead/pack, and rebooted) ubuntu@fili:~$ dpkg -l |grep ureadahead ii ureadahead0.100.0-19.1 amd64Read required files in advance ubuntu@fili:~$ journalctl -b | grep ureadahead | wc -l 3 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Won't Fix Status in ureadahead source package in Xenial: Fix Committed Status in ureadahead source package in Bionic: Fix Released Bug description: [impact] ureadahead logs thousands of lines of useless noise on each boot. [test case] install bionic on physical hardware (ureadhead doesn't run under virt) and check the boot logs: #journalctl -b | grep ureadahead | wc -l 30244 ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it doesn't print as many noise messages (if any), until the pack file is a month or more old, at which time it recreates it (at the next boot) and prints all the noise out again. to reproduce this test case without waiting a month, just remove the pack file and reboot. [regression potential] very little, adding the -q param only causes libnih to switch to quiet mode. any regression would likely be around ureadahead not starting at all, which really wouldn't be that bad anyway, as ureadahead has been removed entirely from Ubuntu starting in cosmic. [other info] original description: -- ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1824804] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824804/+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 1824341] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824341 Title: NoAllowedOrigin cause package removal Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log that happens package removal: $ sudo unattended-upgrade -d [...] Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 257, in call_adjusted self.allowed_origins) File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common marking cliente-ldap for removal (Reading database ... 213413 files and directories currently installed.) Removing cliente-ldap (1:2.17.15) ... marking libcephfs2 for removal (Reading database ... 213392 files and directories currently installed.) Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking ldap-auth-config for removal (Reading database ... 213386 files and directories currently installed.) Removing libpam-ldap:amd64 (186-4ubuntu1) ... Removing ldap-auth-config (0.5.3) ... Removing ldap-auth-client (0.5.3) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking python-samba for removal (Reading database ... 213332 files and directories currently installed.) Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking nss-updatedb for removal (Reading database ... 212865 files and directories currently installed.) Removing nss-updatedb (10-3build1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-vfs-modules for removal (Reading database ... 212859 files and directories currently installed.) Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking librados2 for removal (Reading database ... 212770 files and directories currently installed.) Removing librados2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libibverbs1 for removal (Reading database ... 212761 files and directories currently installed.) Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ... Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libpam-mount for removal (Reading database ... 212731 files and directories currently installed.) Removing libpam-mount (2.16-3ubuntu0.1) ... Processing triggers for sgml-base (1.29) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking ibverbs-providers for removal marking tdb-tools for removal (Reading database ... 212691 files and directories currently installed.) Removing tdb-tools (1.3.15-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-dsdb-modules for removal (Reading database ... 212680 files and directories currently installed.) Removing
[Touch-packages] [Bug 1824949] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824949 Title: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended- upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted::ver_in_allowed_origin Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] * Unattended-upgrades may crash when it tries to find a solution for installing a package that does not have a candidate in any allowed origin. [Test Case] * Watch the error not happening anymore. (It never happened on Xenial) [Regression Potential] * The fix is part of the fix for LP: #1824804 where the crashing code is removed thus there is no additional regression potential. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu2, the problem page at https://errors.ubuntu.com/problem/fbfbd01360a90ba2d6c2620bffdd9e77843e5671 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/unattended-upgrades/+bug/1824949/+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 1824876] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824876 Title: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended- upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu3, the problem page at https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655 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/unattended-upgrades/+bug/1824876/+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 1821103] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821103 Title: [SRU] Skip sending email when no package had to be installed, upgraded or removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Users get unattended-upgrade's email report every day or every time u-u ran, even when no package needed to be upraded, installed or removed. This can annoy administrators managing many servers. * The fix is sending the report email only when there were actions taken by u-u. [Test Case] * The extended autopkgtest script checks if no email is sent when u-u did not upgrade packages. [Regression Potential] * Unattended-upgrades may skip sending emails which would contain useful information, but given the size and the simplicity of the scripts this seems unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821103/+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 1825886] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1825886 Title: Unattended-upgrades may crash when a package does not have a candidate Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Cosmic: New Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * Unattended-upgrades may crash when a package in apt's cache does not have a candidate and it is visited when finding packages to adjust. * The crash occurs when apt.Package.candidate is None and the fix is checking if .candidate is truthy and it that case is safe to reference the .dependencies attribute. [Test Case] * Watch the error not happening anymore. [Regression Potential] * The fix is very small and is not likely to cause any regression. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu5, the problem page at https://errors.ubuntu.com/problem/0d08f995622277f81d276f1eae7e1a722e3627de 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/unattended-upgrades/+bug/1825886/+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 1823872] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: New Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Cosmic: New Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns
[Touch-packages] [Bug 1826157] Proposed package upload rejected
An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: "Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1826157 Title: unattended-upgrades: rewind_cache() may crash due to not adjusting package candidates Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * Unattended-upgrades may crash when rewinding cache due to not adjusting package candidates before marking them to upgrade/install. * The fix is using adjusted marking that in effect rewinds the cache to the right, adjusted state. [Test Case] * test/test_rewind.py is updated to verify that rewinding included adjustments and it is ran during the build. * Also watch the error not happening anymore. [Regression Potential] * The fix is very small and is not likely to cause any regression. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu5, the problem page at https://errors.ubuntu.com/problem/6f57d938f3aa56b3995d5bccf4637d65734d78e4 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/unattended-upgrades/+bug/1826157/+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 1821103] Re: [SRU] Skip sending email when no package had to be installed, upgraded or removed
** Description changed: - . + [Impact] + + * Users get unattended-upgrade's email report every day or every time u-u ran, even when no package needed to be upraded, installed or removed. This can annoy administrators managing many servers. + * The fix is sending the report email only when there were actions taken by u-u. + + [Test Case] + + * The extended autopkgtest script checks if no email is sent when u-u + did not upgrade packages. + + [Regression Potential] + + * Unattended-upgrades may skip sending emails which would contain + useful information, but given the size and the simplicity of the scripts + this seems unlikely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821103 Title: [SRU] Skip sending email when no package had to be installed, upgraded or removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Users get unattended-upgrade's email report every day or every time u-u ran, even when no package needed to be upraded, installed or removed. This can annoy administrators managing many servers. * The fix is sending the report email only when there were actions taken by u-u. [Test Case] * The extended autopkgtest script checks if no email is sent when u-u did not upgrade packages. [Regression Potential] * Unattended-upgrades may skip sending emails which would contain useful information, but given the size and the simplicity of the scripts this seems unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821103/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kbd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Confirmed Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Confirmed Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
** Description changed: [impact] ureadahead logs thousands of lines of useless noise on each boot. [test case] install bionic on physical hardware (ureadhead doesn't run under virt) and check the boot logs: - #journalctl -m | grep ureadahead | wc -l + #journalctl -b | grep ureadahead | wc -l 30244 - - ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it doesn't print as many noise messages (if any), until the pack file is a month or more old, at which time it recreates it (at the next boot) and prints all the noise out again. + ureadahead stores its data in /var/lib/ureadahead/pack so on future + boots, it doesn't print as many noise messages (if any), until the pack + file is a month or more old, at which time it recreates it (at the next + boot) and prints all the noise out again. to reproduce this test case without waiting a month, just remove the pack file and reboot. - [regression potential] very little, adding the -q param only causes libnih to switch to quiet mode. any regression would likely be around ureadahead not starting at all, which really wouldn't be that bad anyway, as ureadahead has been removed entirely from Ubuntu starting in cosmic. [other info] original description: -- ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Won't Fix Status in ureadahead source package in Xenial: Fix Committed Status in ureadahead source package in Bionic: Fix Released Bug description: [impact] ureadahead logs thousands of lines of useless noise on each boot. [test case] install bionic on physical hardware (ureadhead doesn't run under virt) and check the boot logs: #journalctl -b | grep ureadahead | wc -l 30244 ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it doesn't print as many noise messages (if any), until the pack file is a month or more old, at which time it recreates it (at the next boot) and prints all the noise out again. to reproduce this test case without waiting a month, just remove the pack file and reboot. [regression potential] very little, adding the -q param only causes libnih to switch to quiet mode. any regression would likely be around ureadahead not starting at all, which really wouldn't be that bad anyway, as ureadahead has been removed entirely from Ubuntu starting in cosmic. [other info] original description: -- ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1784128] Re: after autoupdate symbols on session screen not func.
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 ** This bug has been marked a duplicate of bug 520546 Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1784128 Title: after autoupdate symbols on session screen not func. Status in console-setup package in Ubuntu: New Bug description: after auto-update password simbols with keyboard on login not func correcly and password ko, when I used keyboard on screen, password ok. when use keyboard on sudo after login password ok. /var/log/apt/history.log Start-Date: 2018-07-27 18:31:46 Commandline: packagekit role='update-packages' Upgrade: console-setup-linux:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), console-setup:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), keyboard-configuration:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3) End-Date: 2018-07-27 18:32:01 lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy console-setup console-setup: Instalados: 1.178ubuntu2.3 Candidato: 1.178ubuntu2.3 Tabla de versión: *** 1.178ubuntu2.3 500 500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.178ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu bionic/main i386 Packages apt-cache policy keyboard-configuration keyboard-configuration: Instalados: 1.178ubuntu2.3 Candidato: 1.178ubuntu2.3 Tabla de versión: *** 1.178ubuntu2.3 500 500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.178ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 28 13:11:52 2018 InstallationDate: Installed on 2018-06-08 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1784128/+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 1822270] Re: Debconf readline frontend does not show options
** Bug watch added: Debian Bug tracker #928182 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928182 ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928182 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Confirmed Status in debconf source package in Xenial: Confirmed Status in debconf source package in Bionic: Confirmed Status in debconf source package in Cosmic: Confirmed Status in debconf source package in Disco: Confirmed Status in debconf source package in Eoan: Confirmed Status in debconf package in Debian: Unknown Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
Hello Christian, or anyone else affected, Accepted unattended-upgrades into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.10ubuntu5.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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: unattended-upgrades (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: New Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Cosmic: New Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_
[Touch-packages] [Bug 1825886] Re: Unattended-upgrades may crash when a package does not have a candidate
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.10ubuntu5.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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: unattended-upgrades (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1825886 Title: Unattended-upgrades may crash when a package does not have a candidate Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Cosmic: New Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * Unattended-upgrades may crash when a package in apt's cache does not have a candidate and it is visited when finding packages to adjust. * The crash occurs when apt.Package.candidate is None and the fix is checking if .candidate is truthy and it that case is safe to reference the .dependencies attribute. [Test Case] * Watch the error not happening anymore. [Regression Potential] * The fix is very small and is not likely to cause any regression. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu5, the problem page at https://errors.ubuntu.com/problem/0d08f995622277f81d276f1eae7e1a722e3627de 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/unattended-upgrades/+bug/1825886/+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 1826157] Re: unattended-upgrades: rewind_cache() may crash due to not adjusting package candidates
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.10ubuntu5.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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: unattended-upgrades (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1826157 Title: unattended-upgrades: rewind_cache() may crash due to not adjusting package candidates Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * Unattended-upgrades may crash when rewinding cache due to not adjusting package candidates before marking them to upgrade/install. * The fix is using adjusted marking that in effect rewinds the cache to the right, adjusted state. [Test Case] * test/test_rewind.py is updated to verify that rewinding included adjustments and it is ran during the build. * Also watch the error not happening anymore. [Regression Potential] * The fix is very small and is not likely to cause any regression. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu5, the problem page at https://errors.ubuntu.com/problem/6f57d938f3aa56b3995d5bccf4637d65734d78e4 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/unattended-upgrades/+bug/1826157/+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 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
Hello Balint, or anyone else affected, Accepted unattended-upgrades into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.10ubuntu5.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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: unattended-upgrades (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824804/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Description changed: [Impact] - * If an update has a new conffile at a path that in a former version was -a directory like - old: /a/b/c - new: a/b -Here b is the new file name and was a directory in the old version. -Then unattended upgrades breaks on installing such a package. + * If an update has a new conffile at a path that in a former version was + a directory like + old: /a/b/c + new: a/b + Here b is the new file name and was a directory in the old version. + Then unattended upgrades breaks on installing such a package. - * a recent qemu update has such a case and due to that triggered the -issue in >=Bionic + * a recent qemu update has such a case and due to that triggered the + issue in >=Bionic - * The fix is to harden unattended upgrades to be able to handle the case -without aborting. + * The fix is to harden unattended upgrades to be able to handle the case + without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: - $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic - $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily + $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic + $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. - $ uvt-kvm ssh bionic-testuu - $ sudo apt update - $ sudo apt dist-upgrade - $ sudo apt install unattended-upgrades - $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 + $ uvt-kvm ssh bionic-testuu + $ sudo apt update + $ sudo apt dist-upgrade + $ sudo apt install unattended-upgrades + $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. - $ sudo unattended-upgrade -d + $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 2057, in - sys.exit(main(options)) - File "/usr/bin/unattended-upgrade", line 1773, in main - if conffile_prompt(item.destfile): - File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt - with open(prefix + conf_file, 'rb') as fp: + File "/usr/bin/unattended-upgrade", line 2057, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1773, in main + if conffile_prompt(item.destfile): + File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt + with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] - TODO: rbalint who writes the fix - * discussion of how regressions are most likely to manifest as a result of this change. - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. + The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] - - * n/a + + * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrade
[Touch-packages] [Bug 1826311] Re: Cannot Login to Google with Advanced Protection Enabled
Thanks, it looks like the bug you are refering to is https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/29 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #29 https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/29 ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/29 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1826311 Title: Cannot Login to Google with Advanced Protection Enabled Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Description: Ubuntu 19.04 Release: 19.04 gnome-online-accounts: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 1) Open Online accounts and select google (From settings or during OS setup) 2) enter username and password. What I expect: I get the prompt to plug-in my 2 factor hardware key What actually happens: I get a prompt saying, "You can only use your Security keys with Google Chrome" Not sure if this is actually fixable, I know desktop firefox has hidden settings to allow u2f, but not sure if that extends to the embedded browsers (if gnome-online-accounts even uses an embedded firefox for its browser) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 00:16:27 2019 InstallationDate: Installed on 2019-04-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1826311/+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 1742941] Re: [18.10] zlib: improve crc32 performance on P8
** Changed in: zlib (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: [18.10] zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Incomplete Status in zlib package in Ubuntu: Incomplete Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1826648] Re: cupds crashes with core dump
Can you please attach your /etc/cups/cupsd.conf, /etc/cups/cups- files.conf, and /etc/cups/printers.conf files. Please also attach your *.ppd files in /etc/cups/ppd/. Also follow the instructions of the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems and then run # cupsd -f -c /etc/cups/cupsd.conf again. Please attach your /var/log/cups/error_log file. Please attach all files one by one. Please do not compress them and do not package them together. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: Incomplete Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826648/+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 1778844] Re: nvme multipath does not report path relationships
Added to the SRU queue on 22nd April. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [
[Touch-packages] [Bug 1826730] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259953/+files/ProcEnviron.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826730] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259950/+files/CurrentDmesg.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826730] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259949/+files/AlsaInfo.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826730] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259951/+files/Dependencies.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826730] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259954/+files/PulseList.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826730] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1826730/+attachment/5259952/+files/ProcCpuinfoMinimal.txt -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1826870] Re: cache.commit() doesn't release the archives lock
** Changed in: python-apt (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Status in python-apt source package in Cosmic: Triaged Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1826730] Re: mp4 audio Crackle when the sound a little loud.
apport-collect is no reponse for a few hours, I think this program need to be rewrite. ** Tags added: apport-collected bionic third-party-packages ** Description changed: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: widon 1517 F pulseaudio + /dev/snd/controlC0: widon 1517 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-11-24 (156 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 + Tags: bionic third-party-packages + Uname: Linux 4.15.0-46-generic x86_64 + UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/13/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X555YI.510 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X555YI + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: X + dmi.product.name: X555YI + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1517 F pulseaudio /dev/snd/controlC0: widon 1517 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-46-generic x86_64 UnreportableReason: 这不是官方的 Ubuntu 软件包。请删除所有第三方软件包，然后重试。 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER
[Touch-packages] [Bug 1826730] Re: mp4 audio Crackle when the sound a little loud.
I don't have "Over-Amplification" enabled. -- 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/1826730 Title: mp4 audio Crackle when the sound a little loud. Status in pulseaudio package in Ubuntu: Incomplete Bug description: both mpv and vlc have this problem, even when I use firefox see youtube video, if I turn the sound a little loud, the sound will with a lot of crackle sound. I ubuntu18.04 all the thing update to date. widon@widon-X555YI:~$ dpkg -l | grep pulseaudio ii gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1amd64GStreamer plugin for PulseAudio ii pulseaudio1:11.1-1ubuntu7.2 amd64PulseAudio sound server ii pulseaudio-module-bluetooth 1:11.1-1ubuntu7.2 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-utils 1:11.1-1ubuntu7.2 amd64Command line tools for the PulseAudio sound server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/+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 1418885] Re: Gstreamer critical warning
Is that still an issue? ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1418885 Title: Gstreamer critical warning Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Hi everybody, I have the following GStreamer-CRITICAL warning and I can't get rid of it: $ gst-launch-1.0 souphttpsrc location="http://IP/video.cgi?videocodec=h264"; user-id=USER user-pw=PASSWORD do-timestamp=true ! multipartdemux ! fakesink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock ^Chandling interrupt. Interrupt: Stopping pipeline ... Execution ended after 0:00:01.692054125 Setting pipeline to PAUSED ... Setting pipeline to READY ... (gst-launch-1.0:12437): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object->refcount > 0' failed Setting pipeline to NULL ... Freeing pipeline ... (For the warning to appear I pressed CTRL-C for stopping the stream.) It seems that it is from the multipartdemux element, if I execute the command without it the warning does not appear. I am using Gstreamer 1.4.5. I saw this link (which seems to describe the problem that I have) but I couldn't use it with Gstreamer 1.0 : https://wiki.archlinux.org/index.php/GStreamer It is very important to me to fix this warning. Can somebody help me with a fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1418885/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Adding fix for Xenial in case the issue turns out more important and we release the fix. The patch needs testing, but should work. ** Patch added: "console-setup_1.108ubuntu15.6.patch" https://bugs.launchpad.net/ubuntu/xenial/+source/console-setup/+bug/520546/+attachment/5259936/+files/console-setup_1.108ubuntu15.6.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: New Status in xorg-server source package in Xenial: New Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1826870] [NEW] cache.commit() doesn't release the archives lock
Public bug reported: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: Triaged ** Affects: python-apt (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #922416 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 ** Also affects: python-apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 Importance: Unknown Status: Unknown ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu) Status: Fix Released => New ** Also affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: python-apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: python-apt (Ubuntu Cosmic) Status: New => Triaged ** Description changed: [Impact] - cache.commit() does not release all the locks it acquires as part of committing. + cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Status in python-apt source package in Cosmic: Triaged Status in python-apt package in Debian: Unknown Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1826870] Re: cache.commit() doesn't release the archives lock
This was fixed in disco, in 1.8.4. It also affects cosmic and bionic; and the proposed SRU for bug 1795407 in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Status in python-apt source package in Cosmic: Triaged Status in python-apt package in Debian: Unknown Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1795407] Re: python-apt frontend locking
Tracking the regression in bug 1826870 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
@paelzer You did not observe the mode change reported by kbd_mode either after the reinstall? Have you unset DISPLAY, too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: New Status in xorg-server source package in Xenial: New Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1795407] Re: python-apt frontend locking
@sil2100 I think there is a regression in the other locking fixes, as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 - but that said, we have that in every other release too, and I'll upload SRUs for that later. ** Bug watch added: Debian Bug tracker #922416 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1821343] Re: slapd process failure is not detected by systemd
** Tags removed: sts-sponsor sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1642514] Update Released
The verification of the Stable Release Update for iproute2 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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1795407] Re: python-apt frontend locking
@juliank is this upload still relevant and good for release? Last time it was 'blocked' on the unattended-upgrades SRU - and that one has landed in xenial-updates already. Can we release it now, or does it need a re-upload? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xenial runs X on VT7 thus in default installations the postinst scripts don't break X. If this fix is scheduled for SRU, please also fix console-setup.postinst, not just keyboard-configuration.postinst. ** Also affects: kbd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: console-setup (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: console-setup (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: New Status in xorg-server source package in Xenial: New Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1642514] Re: sched: Match-all classifier is missing in xenial
This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.5
---
iproute2 (4.3.0-1ubuntu3.16.04.5) xenial; urgency=medium
* sched: Match-all classifier is missing in xenial (LP: #1642514)
- d/p/1011-tc-Add-support-for-the-matchall-traffic-classifier.patch
-- Stefan Bader Thu, 04 Apr 2019 15:47:07
+0200
** Changed in: iproute2 (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1642514] Re: sched: Match-all classifier is missing in xenial
The ubuntu-fan autopkgtest regressions are unrelated and a fix for them
has just been accepted into xenial-proposed (ignoring stderr output).
Ignoring the failure for now and releasing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1821343] Re: slapd process failure is not detected by systemd
This bug was fixed in the package openldap - 2.4.42+dfsg-2ubuntu3.5 --- openldap (2.4.42+dfsg-2ubuntu3.5) xenial; urgency=medium * Fix sysv-generator unit file by customizing parameters (LP: #1821343) - d/slapd-remain-after-exit.conf: Override RemainAfterExit to allow correct systemctl status for slapd daemon. - d/slapd.install: place override file in correct location. -- Heitor Alves de Siqueira Wed, 10 Apr 2019 10:01:36 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
This bug was fixed in the package openldap - 2.4.45+dfsg-1ubuntu1.2 --- openldap (2.4.45+dfsg-1ubuntu1.2) bionic; urgency=medium * Fix sysv-generator unit file by customizing parameters (LP: #1821343) - d/slapd-remain-after-exit.conf: Override RemainAfterExit to allow correct systemctl status for slapd daemon. - d/slapd.install: place override file in correct location. -- Heitor Alves de Siqueira Wed, 10 Apr 2019 09:53:11 -0300 ** Changed in: openldap (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: openldap (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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1816547] Re: SRU 2.56.4 to bionic
There's quite a few autopkgtest regressions reported for this upload. Can someone take a look at it and check if they're related? Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] New upstream bug fix microrelease * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Test various parts of the desktop. - Logging in - Shutting down - Starting a variety of apps and checking that they work + rhythmbox (play a song using gstreamer) + cheese (look at yourself with your webcam using gstreamer) + network-manager + epiphany (web stuff works) Monitor the error tracker for any increases. [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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
