[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
** Changed in: pulseaudio Status: Unknown => 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
The attachment "Set-fSocket-to--1-after-close-on-an-error-to-prevent-a -double-close.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
The fix is now released. Spinning up a new ISO as we speak. calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium * Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805) * Move before_bootloader_mkdirs process before initramfs. * Workaround bug in update-initramfs::get_sorted_versions() with shellprocess. -- Walter Lapchynski Wed, 19 Jun 2019 19:32:14 -0700 ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Walter Lapchynski (wxl) -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) 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 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Also, progress on this issue is now being made upstream: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/509 -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Ubuntu 18.04 is actually the only current release that ships an old version of PulseAudio. Does anyone see this bug in Ubuntu 18.10, 19.04 or 19.10 ? ** Bug watch added: PulseAudio #509 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/509 ** Changed in: pulseaudio Importance: Medium => Unknown ** Changed in: pulseaudio Status: Confirmed => Unknown ** Changed in: pulseaudio Remote watch: freedesktop.org Bugzilla #95104 => PulseAudio #509 -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
This bug was fixed in the package sudo - 1.8.27-1ubuntu2 --- sudo (1.8.27-1ubuntu2) eoan; urgency=medium * Remove d/p/keep_home_by_default.patch (LP: #1556302) - This restores sudo handling of $HOME to what everyone else does -- Dan Streetman Tue, 04 Jun 2019 08:58:02 -0400 ** Changed in: sudo (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** Changed in: keepalived (Ubuntu Cosmic) Status: New => Triaged ** Changed in: keepalived (Ubuntu) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Cosmic) Importance: Undecided => Medium -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in keepalived source package in Bionic: Triaged Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Status in keepalived source package in Cosmic: Triaged Status in netplan.io source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832834] Re: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to freeze anymore, but network traffic stops working. Happend about 1-2 hours after a fresh reboot (after applying updates). It still answered to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or XMPP. After downgrading to 1.1.1b-1ubuntu2.1 it's now running for 3 hours without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832834 Title: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2 Status in openssl package in Ubuntu: New Bug description: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Patch added: "Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch" https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I'm marking this a security bug, since all double close bugs can potentially be security bugs in multithreaded programs depending on the close interleaving. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
See kodi issue with stack traces: https://github.com/xbmc/xbmc/issues/16258 ** Also affects: jackd2 (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] [NEW] libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
*** This bug is a security vulnerability *** Public security bug reported: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Affects: jackd2 (Debian) Importance: Undecided Status: New ** Bug watch added: github.com/xbmc/xbmc/issues #16258 https://github.com/xbmc/xbmc/issues/16258 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1768166] Re: Random crashes
I tried your ibus-pinyin ppa; the problem still persists. I will explain
that in better detail later. Basically, after 18.04 (no problem there),
ibus-pinyin fails to update the hierarchy of an "entered" word or phase in
the "candidate list". This is one of the most important features of a
Chinese input tool. Without it, thhis tool is unusable.
The Chinese Ubuntu forum member who helped testing ibus-libpinyin 1.11
(百草谷居--btw, he is also a CPA）mentioned two important features that are
lacking in ibus-libpinyin which actually also prevented him from using this
input tool (except for doing this test). Both features are available (&
kicking) in ibus-pinyin.
However, my most critical concern is always about stability. I have used
the same old ibus-pinyin Chinese input tool since 18.04 daily built first
became available and have not had any problem. As I mentioned in previous
communications, for some unknown reason ibus-pinyin doesn't work well in
Fedora/RedHat (though it can be installed without any problem), in reasons
probably similar to why ibus-pinyin is not working well in 19.04/19.10.
This is the main reason that I am not too thrilled about Fedora.
On Wed, Jun 19, 2019 at 12:42 AM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:
> Thanks Ping-Wu!
>
> Our attempts to recruit additional Chinese testers failed unfortunately.
> My view is that we still are ready to consider the proposed packages
> verified. I base my view on:
>
> * The bug reporter's test results according to comment #35
>
> * My own verification measures according to comment #23
>
> * The reporter of bug #1829947 expressed a positive testimony as to
> the ibus-libpinyin version we are backporting here (comment #20 in
> that report).
>
> * The proposed packages have 'matured' in -proposed for soon three
> weeks.
>
> ** Tags removed: verification-needed verification-needed-bionic
> verification-needed-cosmic
> ** Tags added: verification-done verification-done-bionic
> verification-done-cosmic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
> Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
> Fix Released
> Status in libpinyin package in Ubuntu:
> Fix Released
> Status in ibus-libpinyin source package in Bionic:
> Fix Committed
> Status in libpinyin source package in Bionic:
> Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
> Fix Committed
> Status in libpinyin source package in Cosmic:
> Fix Committed
>
> Bug description:
> [Impact]
>
> ibus-libpinyin has proved to crash far too often. One or more files in
> ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
> directory allows the user to keep using ibus-libpinyin.
>
> In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
> present, and the number of crashes has been reduced significantly:
>
> https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
>
> Upstream ChangeLog ibus-libpinyin:
> --
> version 1.11.0
> * fixes keypad decimal
> * fixes emoji candidates
> * support configurable opencc config
>
> version 1.10.92
> * fixes Enter handling
>
> version 1.10.91
> * support ime.register_trigger in lua extension
> * support predicted candidates
> * support emoji input
>
> version 1.10.0
> * bug fixes
>
> version 1.9.91
> * migrate to use GSettings
> * fixes lyx short cut issue
>
> version 1.9.3
> * translate input method name in ibus menu
>
> Upstream ChangeLog libpinyin:
> -
> version 2.2.2
> * minor fixes
>
> version 2.2.1
> * fixes predicted candidates
>
> version 2.2.0
> * bug fixes
>
> The proposal is to backport the disco versions of those packages to
> bionic and cosmic in an attempt to prevent crashes. Proposed uploads
> are available in this PPA:
>
> https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
> [Test Case]
>
> * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
> * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
> (This is apparently not a confirmation that the upload really fixes
> the bug. To compensate for that, we will await testing of the
> -proposed packages by a few Chinese users before considering the
> uploads verified.)
>
> Reverse dependencies
>
> Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend
> on packages belonging to the libpinyin source package. So additional test
> measures are:
>
> * Install fcitx-libpinyin and ibus-libzhuyin.
>
> * Use both those tools for typing Chinese, and confirm that you don't
> observe any adverse effects of the libpinyin upgrade.
>
> [Regression Potential]
>
> The changes are mostly bug fixes, so the regression
[Touch-packages] [Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Given SRU and backport team policies, having a newer version of keepalived in bionic seems pretty unlikely. SRU policy favors backports of specific fixes rather than entire package backports, while the backports team generally discourages backports of libraries or services since they can randomly break other software using them. So, the most practical route forward would be to identify the patch(es) needed for fixing the particular issue at hand, and go through the regular SRU process. I am, unfortunately, completely unfamiliar with keepalived, but attached is a list of upstream comments mentioning "VIP" since the v.1.3.9 release, which I generated like this: git log --grep="VIP" v1.3.9.. > /tmp/vip_commits.txt The next step would be for someone more familiar than me, to review the list and identify 1 or 2 patches worth testing. Then apply the patch to the bionic keepalived package and test for a fix. After we know what patch is needed, an SRU request can be placed to have it released for all users. ** Attachment added: "vip_commits.txt" https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+attachment/5271627/+files/vip_commits.txt ** Changed in: keepalived (Ubuntu) Status: Confirmed => Triaged -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in keepalived source package in Bionic: New Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Status in keepalived source package in Cosmic: New Status in netplan.io source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Oh, one other thing that will be necessary to file an SRU for this would be a a series of "paint by number" steps to reproduce the issue, and to verify the fix. For example, something akin to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583/comments/12 ** Also affects: keepalived (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in keepalived source package in Bionic: New Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Status in keepalived source package in Cosmic: New Status in netplan.io source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] [NEW] libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
Public bug reported: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in openssl package in Ubuntu: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output:
[Touch-packages] [Bug 1832882] Re: libcurl-gnutls segfaults spotify client
** Tags added: rls-dd-incoming ** Also affects: curl (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: curl (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Confirmed Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833198] Re: CURL shipped with Ubuntu 18.04 contained bug #2303
The current development release of Ubuntu does not contain this bug so I'm setting that task to Fix Released. ** Also affects: curl (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: curl (Ubuntu Bionic) Status: New => Triaged ** Changed in: curl (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: curl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1833198 Title: CURL shipped with Ubuntu 18.04 contained bug #2303 Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: Triaged Bug description: Ubuntu 18.04 lsb_release -rd Description: Ubuntu 18.04.2 LTS ships with cURL version ... apt-cache policy curl curl: Installed: 7.58.0-2ubuntu3.7 Candidate: 7.58.0-2ubuntu3.7 Version table: *** 7.58.0-2ubuntu3.7 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 7.58.0-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages which contains bug #2303 https://github.com/curl/curl/issues/2303 The Ubuntu package needs to updated to take a version that contains a fix for this bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1833198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Description changed: + [impact] + + sudo does not set HOME to the target user's HOME + + [test case] + + ddstreet@thorin:~$ sudo printenv | grep HOME + HOME=/home/ddstreet + + [regression potential] + + this is a significant behavior change. As mentioned in comment 11 (and + later, and other bugs duped to this, and the mailing list discussion, + etc) users of Ubuntu so far have been used to running sudo with their + own HOME set, not root's HOME. Therefore, it's inappropriate to change + this behavior for existing releases; this should be changed starting in + Eoan, and only the sudo and sudoers man pages changed in previous + releases to indicate the actual behavior of sudo in those releases. + + [other info] + + Shortly after upstream changed the behavior, the patch to keep HOME as + the calling (instead of target) user was added in bug 760140. + + For quick reference to anyone coming to this bug, the pre-19.10 behavior + (of sudo keeping the calling user's $HOME) can be disabled by running + 'sudo visudo' and adding this line: + + Defaultsalways_set_home + + or, run sudo with the -H param. + + -- + original description: + -- + I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. - - -- - - Note: for quick reference to anyone coming to this bug, this behavior - (of sudo keeping the calling user's $HOME) can be disabled by running - 'sudo visudo' and adding this line: - - Defaultsalways_set_home -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: In Progress Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: In Progress Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that
[Touch-packages] [Bug 1833470] [NEW] ca0132 audio in Ubuntu 19.04 only after Windows 10 started
Public bug reported: Motherboard: Gigabyte GA-Z170X-Gaming GT (rev. 1.0) Description: Ubuntu 19.04 Release: 19.04 Expected behavior: Audio playback via headphones Actual behavior: No audio playback heard If I start Ubuntu 19.04 directly after booting my PC, there is no sound from the front or rear outputs. Everything seems configured correctly in Alsamixer, etc. If I boot into Windows 10, then restart and enter Ubuntu, the sound works as expected. I suspect something is being set properly by the Windows driver that is missed in the native Linux driver. The fact that it survives a (soft) reboot is interesting. I know this is at the ALSA level or below, because if I stop pulseaudio, `aplay music.wav` produces no output before starting Windows, and works after starting Windows. output of `lspci | grep -i audio` 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 02:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) output of `aplay -lL` default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, CA0132 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Digital IEC958 (S/PDIF) Digital Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 1 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 2 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 3 HDMI Audio Output dmix:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample mixing device dmix:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample mixing device dmix:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample mixing device dmix:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample mixing device dsnoop:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample snooping device dsnoop:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample snooping device dsnoop:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample snooping device dsnoop:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample snooping device hw:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct hardware device without any conversions hw:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct hardware device without any conversions hw:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct hardware device without any conversions hw:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct hardware device without any conversions plughw:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Hardware device with all software conversions plughw:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Hardware device with all software conversions plughw:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Hardware device with all software conversions plughw:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Hardware device with all software conversions usbstream:CARD=NVidia HDA NVidia USB Stream Output List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], d
[Touch-packages] [Bug 889936] Re: sudo(8) incorrectly says HOME is reset if env_reset is set
*** This bug is a duplicate of bug 1556302 *** https://bugs.launchpad.net/bugs/1556302 ** This bug has been marked a duplicate of bug 1556302 Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/889936 Title: sudo(8) incorrectly says HOME is reset if env_reset is set Status in sudo package in Ubuntu: Confirmed Bug description: Version: 1.7.4p6-1ubuntu2 on Ubuntu 11.10 What happens: sudo(8) contains "By default, sudo will set HOME if env_reset or always_set_home are set" and "Set to the home directory of the target user if -i or -H are specified, env_reset or always_set_home are set in sudoers" What I expect to happen: sudo(8) should not claim that HOME is set if env_reset is set. I believe sudo(8) should not claim this because sudo does /not/ set HOME if env_reset is set, which is the expected behaviour according to https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140 . This behaviour is what happens when env_reset is set (I have attached my /etc/sudoers, which is the default Ubuntu /etc/sudoers): $ sudo env | grep HOME HOME=/home/tom $ sudo -H env | grep HOME HOME=/root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/889936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823202] Re: HOME points to something not owned by user in sudo
*** This bug is a duplicate of bug 1556302 *** https://bugs.launchpad.net/bugs/1556302 ** This bug is no longer a duplicate of bug 889936 sudo(8) incorrectly says HOME is reset if env_reset is set ** This bug has been marked a duplicate of bug 1556302 Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1823202 Title: HOME points to something not owned by user in sudo Status in sudo package in Ubuntu: New Status in zsh package in Ubuntu: New Bug description: You shouldn't use interactive shell, or any program with executable configuration, while your HOME points to something not owned by your user. That's the big issue and it's with sudo, not zsh, not omz, not any other shell or application you launch. You can go shout "you are doing security wrong" at Ubuntu. Good luck. ╭─rkm@Khadas ~ ╰─➤ id rkm && getent passwd rkm uid=1001(rkm) gid=1001(rkm) groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access) rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh ╭─rkm@Khadas ~ ╰─➤ sudo /usr/bin/env 1 ↵ LC_MESSAGES=en_US.UTF-8 LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 TERM=xterm-256color XAUTHORITY=/home/rkm/.Xauthority COLORTERM=truecolor DISPLAY=:0.0 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin HOME=/home/rkm LC_CTYPE=en_US.UTF-8 LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: MAIL=/var/mail/root LOGNAME=root USER=root USERNAME=root SHELL=/bin/bash SUDO_COMMAND=/usr/bin/env SUDO_USER=rkm SUDO_UID=1001 SUDO_GID=1001 ╭─rkm@Khadas ~ ╰─➤ CyberManifest: sudo is a package. Also, once filed, add zsh to the bug since it could be a bug in zsh's package as well. Not necessarily zsh itself, but the packaging. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 Uname: Linux 4.9.40 aarch64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 CurrentDesktop: XFCE Date: Thu Apr 4 11:07:42 2019 SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1823202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 606195] Re: manpage confused about mail_badpass vs always_set_home
** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/606195 Title: manpage confused about mail_badpass vs always_set_home Status in sudo package in Ubuntu: Fix Released Bug description: Binary package hint: sudo lucid sudoers(5) says mail_badpassIf set, sudo will set the HOME environment variable to the home directory of the target user (which is root unless the -u option is used). This effectively means that the -H option is always implied. This flag is off by default. however this description is fairly obviously about always_set_home not mail_badpass. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: sudo 1.7.2p1-1ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic i686 Architecture: i386 CheckboxSubmission: a72aa433ee7cbc70b12a74f6938b856b CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f Date: Fri Jul 16 11:39:21 2010 ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/zsh SourcePackage: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/606195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832659] Re: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350
It looks like the verification-done-bionic tag was added, so I don't understand this comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832659 Title: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Regression was introduced in OpenSSL 1.1.1 and fixed in 1.1.1b that prevents initialising libcrypto/libssl multiple times, and/or with different options. * This breaks existing applications that correctly use init API, ie. initialise libcrypto before/separately from libssl and/or with different options. [Test Case] * wget https://bugs.launchpad.net/ubuntu/cosmic/+source/openssl/+bug/1832659/+attachment/5270802/+files/test_multiple_libssl_libcrypto_init.py * python3 ./test_multiple_libssl_libcrypto_init.py test_multiple_init (__main__.TestMultipleInit) ... ok -- Ran 1 test in 0.014s OK [Regression Potential] * This is a cherrypick from upstream, and is backwards compatible with existing code. Simply init succeeds under more conditions now, than it did previously in 1.1.1. Also with this fix, OpenSSL is back to how things used to work with 1.1.0 and prior releases. [Original Bug report] After the update of openssl in bionic, I started having an issue and after troubleshooting found this issue: https://github.com/openssl/openssl/issues/7350 Applying the patch linked in that issue and rebuilding the openssl package avoided the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu Jun 13 00:21:16 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1832659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691314] Re: Completions should be paged through PAGER when `page-completions` is off
This was brought up previously on the bash mailing list in 2014: https://lists.gnu.org/archive/html/help-bash/2014-03/msg00017.html and then the readline mailing list: https://lists.gnu.org/archive/html/bug-readline/2014-03/msg00044.html and elsewhere: https://lists.debian.org/debian-user/2014/04/msg00138.html https://stackoverflow.com/questions/26257724/set-less-as-pager-in-psql https://unix.stackexchange.com/questions/158269/can-we-use-something- better-than-more-for-tab-completion But implementing an external pager is not an easy task, and so far it looks like nobody has done so. >> I had a look at the source already, realizing that the internal paging >> mechanism is quite entangled within readline. I even considered trying >> a patch myself by passing the output to popen() to talk to the external >> pager. > I would have to see whether or not a popen-style approach would work with > applications that want to manage the terminal in other ways, its effect on > any signal handling applications want to do, and whether or not it would > work in a callback-oriented application. https://lists.gnu.org/archive/html/bug-readline/2014-03/msg00046.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1691314 Title: Completions should be paged through PAGER when `page-completions` is off Status in bash package in Ubuntu: New Bug description: When tab completion sends output through a pager, it seemed to use more. Because less is better than more, I wanted it to use less instead, particularly so I can scroll in both directions. I initially made /bin/more a symlink to less (which would trigger its more-emulation mode, but that's still better than actual more), but this had no effect. As a result, I consulted the man page for bash. In the section on readline, there is a setting `page-completions` which says that when on (the default), readline will use a built-in more- like pager to page the results. This doesn't specify what happens when it is turned off, but I expected that instead of the built-in pager, it would use an external on, specifically the one specified in the PAGER environment variable. However, it instead simply dumps the results in the terminal. Please add some way to use PAGER as the pager for completion results. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 16 18:42:43 2017 InstallationDate: Installed on 2016-04-27 (384 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1691314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
This bug was fixed in the package evince - 3.28.4-0ubuntu1.2
---
evince (3.28.4-0ubuntu1.2) bionic-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus system bus (we allow full
access to session, translation and accessibility buses for compatibility)
+ allow Get* to anything polkit allows
+ allow talking to avahi (for printing)
+ allow talking to colord (for printing)
- make the thumbnailer more restrictive (LP: #1794848) (Closes: #909849)
+ remove evince abstraction and use only what is needed from it
+ limit access to DBus session bus
+ generally disallow writes
+ allow reads for non-hidden files
* debian/apparmor-profile.abstraction: apply hardening from Ubuntu 18.10
- disallow access to the dirs of private files (LP: #1788929)
* debian/apparmor-profile: allow /bin/env ixr
-- Jamie Strandboge Tue, 18 Jun 2019 19:15:55 +
** Changed in: evince (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Released
Status in evince source package in Trusty:
Won't Fix
Status in apparmor source package in Xenial:
Fix Released
Status in evince source package in Xenial:
Fix Released
Status in apparmor source package in Bionic:
Fix Released
Status in evince source package in Bionic:
Fix Released
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Released
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To
[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
This bug was fixed in the package evince - 3.18.2-1ubuntu4.5
---
evince (3.18.2-1ubuntu4.5) xenial-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus system bus (we allow full
access to session, translation and accessibility buses for compatibility)
+ allow Get* to anything polkit allows
+ allow talking to avahi (for printing)
+ allow talking to colord (for printing)
- make the thumbnailer more restrictive (LP: #1794848) (Closes: #909849)
+ remove evince abstraction and use only what is needed from it
+ limit access to DBus session bus
+ generally disallow writes
+ allow reads for non-hidden files
* debian/apparmor-profile.abstraction: apply hardening from Ubuntu 18.10
- disallow access to the dirs of private files (LP: #1788929)
* debian/apparmor-profile: allow /bin/env ixr
-- Jamie Strandboge Tue, 18 Jun 2019 19:28:02 +
** Changed in: evince (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Released
Status in evince source package in Trusty:
Won't Fix
Status in apparmor source package in Xenial:
Fix Released
Status in evince source package in Xenial:
Fix Released
Status in apparmor source package in Bionic:
Fix Released
Status in evince source package in Bionic:
In Progress
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Released
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To
[Touch-packages] [Bug 1832659] Reminder of SRU verification policy change
Thank you for taking the time to verify this stable release fix. We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE). Please remove the verification-done tag and add one for the release you have tested the package in. Thank you! https://wiki.ubuntu.com/StableReleaseUpdates#Verification -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832659 Title: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Regression was introduced in OpenSSL 1.1.1 and fixed in 1.1.1b that prevents initialising libcrypto/libssl multiple times, and/or with different options. * This breaks existing applications that correctly use init API, ie. initialise libcrypto before/separately from libssl and/or with different options. [Test Case] * wget https://bugs.launchpad.net/ubuntu/cosmic/+source/openssl/+bug/1832659/+attachment/5270802/+files/test_multiple_libssl_libcrypto_init.py * python3 ./test_multiple_libssl_libcrypto_init.py test_multiple_init (__main__.TestMultipleInit) ... ok -- Ran 1 test in 0.014s OK [Regression Potential] * This is a cherrypick from upstream, and is backwards compatible with existing code. Simply init succeeds under more conditions now, than it did previously in 1.1.1. Also with this fix, OpenSSL is back to how things used to work with 1.1.0 and prior releases. [Original Bug report] After the update of openssl in bionic, I started having an issue and after troubleshooting found this issue: https://github.com/openssl/openssl/issues/7350 Applying the patch linked in that issue and rebuilding the openssl package avoided the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu Jun 13 00:21:16 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1832659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
** Changed in: systemd (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829347
Title:
systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
Incomplete
Status in systemd source package in Cosmic:
Incomplete
Status in systemd source package in Disco:
Incomplete
Status in systemd source package in Eoan:
Won't Fix
Status in systemd package in Debian:
New
Bug description:
[impact]
systemd autopkgtest fails
[test case]
run systemd autopkgtest, check for output like:
LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
FAIL
==
FAIL: test_luks_tmp (__main__.CryptsetupTest)
LUKS device with "tmp" option
--
Traceback (most recent call last):
File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59,
in setUp
self.fail('%s exists already' % self.plaintext_dev)
AssertionError: /dev/mapper/testcrypt1 exists already
or for older releases something like:
autopkgtest [19:27:26]: test storage: [---
modprobe: FATAL: Module scsi_debug not found in directory
/lib/modules/4.18.0-1011-kvm
ERROR
==
ERROR: setUpClass (__main__.CryptsetupTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21,
in setUpClass
subprocess.check_call(['modprobe', 'scsi_debug'])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned
non-zero exit status 1.
this has attempted to be fixed in disco/eoan so the output is a bit
different across different releases, but all of them have the common
point of failing to modprobe or rmmod the scsi_debug module, which by
itself doesn't indicate a failure.
[regression potential]
low; this is fixing a testcase only.
[other info]
fixing test case that generally causes the failed rmmod in bug 1831459
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833450] Re: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- 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/1833450 Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in python2.7 package in Ubuntu: New Bug description: when i opened my system, this bug occurred. I don't know what's the issue. I've found so many things but not working in this case. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 19 08:25:58 2019 DuplicateSignature: package:libpython2.7-dev:2.7.15~rc1-1ubuntu0.1 Unpacking python2.7-dev (2.7.15-4ubuntu4~18.04) over (2.7.15~rc1-1ubuntu0.1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2018-12-22 (178 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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.11 SourcePackage: python2.7 Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1833450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833450] [NEW] package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: when i opened my system, this bug occurred. I don't know what's the issue. I've found so many things but not working in this case. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 19 08:25:58 2019 DuplicateSignature: package:libpython2.7-dev:2.7.15~rc1-1ubuntu0.1 Unpacking python2.7-dev (2.7.15-4ubuntu4~18.04) over (2.7.15~rc1-1ubuntu0.1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2018-12-22 (178 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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.11 SourcePackage: python2.7 Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check third-party-packages -- 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/1833450 Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in python2.7 package in Ubuntu: New Bug description: when i opened my system, this bug occurred. I don't know what's the issue. I've found so many things but not working in this case. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 19 08:25:58 2019 DuplicateSignature: package:libpython2.7-dev:2.7.15~rc1-1ubuntu0.1 Unpacking python2.7-dev (2.7.15-4ubuntu4~18.04) over (2.7.15~rc1-1ubuntu0.1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2018-12-22 (178 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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.11 SourcePackage: python2.7 Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1833450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4
Hello Iain, or anyone else affected, Accepted glib2.0 into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.60.4-0ubuntu0.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-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: glib2.0 (Ubuntu Disco) Status: In Progress => 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Disco: Fix Committed Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do n
[Touch-packages] [Bug 1807627] Re: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
This affected me too, breaking a system in the middle of a release upgrade. I got out of that situation by: 1. Temporarily commenting out entries in /usr/lib/tmpfiles.d/journal- nocow.conf 2. Running: dpkg --configure -a 3. Running: apt-get -f install 4. Running: apt full-upgrade 5. Restoring entries in /usr/lib/tmpfiles.d/journal-nocow.conf 6. Reboot -- 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/1807627 Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: during upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Dec 9 17:11:50 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-09-01 (829 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=aa4fc23f-9987-40c4-8278-a702ff0b99a3 ro RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.2.29 SourcePackage: systemd Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.21 dmi.board.asset.tag: 2UA142177C dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA142177C dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.21:bd06/20/2012:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445625] Re: Change the default RSA generation from 2048 to 3072
This bug was fixed in the package openssh - 1:8.0p1-2 --- openssh (1:8.0p1-2) experimental; urgency=medium * Fix interop tests for recent regress changes. -- Colin Watson Fri, 14 Jun 2019 14:32:12 +0100 ** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1445625 Title: Change the default RSA generation from 2048 to 3072 Status in openssh package in Ubuntu: Fix Released Bug description: For security purposes, the Ubuntu Distro should consider changing the default RSA generation from 2048 to 4096. This is a could be a somewhat disruptive change (e.g. accessing older Cisco devices may not work). We should still try to consider this and target this for 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1445625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828215] Re: openssl ca -spkac output regressed
This bug was fixed in the package openssl - 1.1.1c-1ubuntu2 --- openssl (1.1.1c-1ubuntu2) eoan; urgency=medium * Bump major version of OpenSSL in postinst to trigger services restart upon upgrade. Many services listed there must be restarted when upgrading 1.1.0 to 1.1.1. LP: #1832522 * Fix path to Xorg for reboot notifications on desktop. LP: #1832421 -- Dimitri John Ledkov Thu, 13 Jun 2019 15:29:07 +0100 ** Changed in: openssl (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Committed Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] Setup CA: $ apt install openssl $ mkdir -p demoCA/private demoCA/newcerts $ touch demoCA/index.txt $ echo 01 > demoCA/serial $ openssl req -new -x509 -days 365 -newkey rsa:4096 -keyout demoCA/private/cakey.pem -out demoCA/cacert.pem # Use password test # Accept defaults for all other settings $ openssl req -new -days 365 -newkey rsa:4096 -keyout demoCA/sslkey.pem -out demoCA/sslcert.pem Generate regular request / key: # Use password test # Set common name to: example.com # Accept defaults for all other settings Generate spkac request: $ openssl spkac -key demoCA/sslkey.pem -out demoCA/sslcert.spkac $ cat <>demoCA/sslcert.spkac countryName=AU stateOrProvinceName=Some-State organizationName=Internet Widgits Pty Ltd commonName=example.com EOF Sign spkac request: $ echo test | openssl ca -passin stdin -batch -spkac demoCA/sslcert.spkac -startdate 190121130654Z Expected: pure text output Unexpected: binary output for the signed cert Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665695] Re: OpenSSH PKCS#11 interface does not support ECC.
This bug was fixed in the package openssh - 1:8.0p1-2 --- openssh (1:8.0p1-2) experimental; urgency=medium * Fix interop tests for recent regress changes. -- Colin Watson Fri, 14 Jun 2019 14:32:12 +0100 ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1665695 Title: OpenSSH PKCS#11 interface does not support ECC. Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard ssh-keygen -v -D /usr/lib/libeTPkcs11.so debug1: manufacturerID cryptokiVersion 2.20 libraryDescription libraryVersion 9.1 debug1: label manufacturerID model serial <> flags 0x60d C_GetAttributeValue failed: 18 debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa no keys cannot read public key from pkcs11 pkcs11-tool --module /usr/lib/libeTPkcs11.so -O ... Public Key Object; EC EC_POINT 256 bits EC_POINT: 04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc EC_PARAMS: 06082a8648ce3d030107 label: TestECCpair Usage: encrypt, verify, wrap There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728 release: Ubuntu 16.04.2 LTS openssh version: 7.2p2-4ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1665695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798049] Re: ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt
This bug was fixed in the package openssh - 1:8.0p1-2 --- openssh (1:8.0p1-2) experimental; urgency=medium * Fix interop tests for recent regress changes. -- Colin Watson Fri, 14 Jun 2019 14:32:12 +0100 ** Changed in: openssh (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1798049 Title: ssh ConnectTimeout is obeyed only on 1st ConnectionAttempt Status in openssh package in Ubuntu: Fix Released Bug description: This seems a regression from Ubuntu 17.10 OpenSSH 7.5. Setting the SSH option ConnectTimeout=N only works on the first ConnectionAttempts. So, if you set ConnectionAttempts=2 for example, it will time out after N second on the first attempt and wait the full, default TCP timeout on the second attempt. Example of the error: $ time ssh - -o ConnectTimeout=2 -o ConnectionAttempts=2 -o StrictHostKeyChecking=false -o UserKnownHostsFile=/dev/null 1.2.3.4 OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /home/vide/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "1.2.3.4" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22. debug2: fd 3 setting O_NONBLOCK debug1: connect to address 1.2.3.4 port 22: Connection timed out debug1: Trying again... debug1: Connecting to 1.2.3.4 [1.2.3.4] port 22. debug1: connect to address 1.2.3.4 port 22: Connection timed out ssh: connect to host 1.2.3.4 port 22: Connection timed out real2m13,670s user0m0,012s sys 0m0,018s The first timeout happens after 2 seconds, the second after ~2 minutes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 10:48:41 2018 InstallationDate: Installed on 2017-11-20 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1798049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661745] Re: ssh-keyscan does not exit with non-zero return code on error
This bug was fixed in the package openssh - 1:8.0p1-2 --- openssh (1:8.0p1-2) experimental; urgency=medium * Fix interop tests for recent regress changes. -- Colin Watson Fri, 14 Jun 2019 14:32:12 +0100 ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1661745 Title: ssh-keyscan does not exit with non-zero return code on error Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh package in Debian: Fix Released Bug description: On xenial, ssh-keyscan returns zero indicating success, when the command fails. root@cp1:~# lsb_release -d Description: Ubuntu 16.04.1 LTS root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@cp1:~# echo $? 0 On trusty, the exit status is non-zero as expected. root@integration-deployer:/home/ubuntu# lsb_release -d Description: Ubuntu 14.04.5 LTS root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host getaddrinfo bad-host: Name or service not known root@integration-deployer:/home/ubuntu# echo $? 255 This is a incompatibility between Ubuntu 14.04 and 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1661745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832421] Re: openssl reboot needed message using incorrect path to X server
This bug was fixed in the package openssl - 1.1.1c-1ubuntu2 --- openssl (1.1.1c-1ubuntu2) eoan; urgency=medium * Bump major version of OpenSSL in postinst to trigger services restart upon upgrade. Many services listed there must be restarted when upgrading 1.1.0 to 1.1.1. LP: #1832522 * Fix path to Xorg for reboot notifications on desktop. LP: #1832421 -- Dimitri John Ledkov Thu, 13 Jun 2019 15:29:07 +0100 ** Changed in: openssl (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832421 Title: openssl reboot needed message using incorrect path to X server Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Committed Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * On desktop, upgrading libssl1.1 does not show reboot required notification [Test Case] * Boot ubuntu desktop * Upgrade libssl1.1 * Observe reboot notification pop-up from update-notifier is _not_ shown [Regression Potential] * Tweaking postinst only to correct for the Xorg path. Current code is innert, but is well excercised in prior releases. [Other Info] * Original bug report: Hello, the openssl library postinst file is using pidof /usr/bin/X, but that doesn't appear to be the path to the X11 server any more: debian/libssl1.1.postinst: # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/bin/X > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi On my 18.04 LTS laptop: $ ps auxw | grep Xorg root 2440 0.5 0.4 495932 78996 tty7 Rsl+ May10 264:45 /usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Jun 11 18:06:51 2019 InstallationDate: Installed on 2012-10-18 (2427 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832522] Re: openssl maintainer scripts do not trigger services restart
This bug was fixed in the package openssl - 1.1.1c-1ubuntu2 --- openssl (1.1.1c-1ubuntu2) eoan; urgency=medium * Bump major version of OpenSSL in postinst to trigger services restart upon upgrade. Many services listed there must be restarted when upgrading 1.1.0 to 1.1.1. LP: #1832522 * Fix path to Xorg for reboot notifications on desktop. LP: #1832421 -- Dimitri John Ledkov Thu, 13 Jun 2019 15:29:07 +0100 ** Changed in: openssl (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832522 Title: openssl maintainer scripts do not trigger services restart Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * Major libssl ugprades require services to be restarted, for them to continue to function correctly at runtime. * The maintainer scripts were not adjusted to trigger. [Test Case] * Install bionic from release pocket and install ssl using daemon e.g. openssh-server libapache-mod-ssl * Upgrade libssl1.1 * Ensure that services that use openssl are offered to be restarted. [Regression Potential] * We are rebuilding libssl1.1 and changing maintainer scripts. Given that we have missed upgrade trigger, we will ask users to restart services again even if they may have restarted them already. [Other Info] * Previous major libssl upgrade issue of similar nature was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743889 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833443] Re: Calculator button does nothing (Calculator not launched)
** Package changed: systemd (Ubuntu) => udev (Ubuntu) -- 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/1833443 Title: Calculator button does nothing (Calculator not launched) Status in udev package in Ubuntu: New Bug description: Troubleshoot steps followed: https://wiki.ubuntu.com/Hotkeys/Troubleshooting. I can try provide info from https://wiki.ubuntu.com/DebuggingProcedures if wanted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.22 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_51_55_generic_52 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.warzone2100.rules 70-snap.core.rules 70-snap.opendungeons.rules 56-hpmud.rules S99-2000S1.rules 70-snap.minetest.rules 40-libsane.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules Date: Wed Jun 19 17:58:19 2019 InstallationDate: Installed on 2019-05-14 (36 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=9b9d08ae-0424-4d09-87e0-5db4115b3a2b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.60 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.60:bd03/12/2015:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1833443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
On Wed, 19 Jun 2019, 16:30 Sascha Silbe,
wrote:
>
> This update breaks salt-ssh 2016.11.2 (started from a different computer
> that's running Debian Stretch) on Ubuntu 18.04 (running on the machine
> being managed). Having Salt break from one day to the next for managing
> an LTS (!) release is a rather major PITA.
salt 2016 is an old obsolete version. Ubuntu 18.04 ships salt 2017.
this regression was already identified, and an update to address
compatibility with older software is being staged in bionic-proposed.
See for more details
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832659
>
> Curiously enough, salt-ssh 2016.11.2 continues to work just fine on
> minions running Ubuntu 19.04 which ships openssl 1.1.1b-1ubuntu2.1. So
> whatever this SRU does apparently is different from how it works on
> Ubuntu 19.04.
>
Have you tried openssl 1.1.1-1ubuntu2.1~18.04.3 from bionic proposed?
If that one helps, please leave a comment on
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832659 to help
us release the update sooner.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in libio-socket-ssl-perl source package in Bionic:
Fix Released
Status in libnet-ssleay-perl source package in Bionic:
Fix Released
Status in libwww-perl source package in Bionic:
Fix Released
Status in openssl source package in Bionic:
Fix Released
Status in python-cryptography source package in Bionic:
Fix Released
Status in python-tornado source package in Bionic:
Fix Committed
Status in python2.7 source package in Bionic:
Fix Released
Status in python3.6 source package in Bionic:
Fix Released
Status in python3.7 source package in Bionic:
Fix Released
Status in r-cran-openssl source package in Bionic:
Fix Released
Status in ruby-openssl source package in Bionic:
Fix Released
Status in ruby2.5 source package in Bionic:
Fix Released
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.
[Test Case]
* Rebuild all reverse dependencies
* Execute autopkg tests for all of them
* Clamp down to TLS v1.2 software that does not support TLS v1.3
(e.g. mongodb)
* Backport TLS v1.3 support patches, where applicable
[Test cases for the python updates]
python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.
python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.
python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.
The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
And analyzed in
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
[ Test case libwww-perl (and deps) regression ]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
1. apt install liblwp-protocol-https-perl
2. enable -proposed
3. apt install libio-socket-ssl-perl libnet-ssleay-perl
4. perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or die'
[Regression Potential]
* Connectivity interop is the biggest issues which will be
unavoidable with introducing TLS v1.3. However, tests on cosmic
demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
negotiate TLS v1.3 without issues.
* Mitigation of disco
[Touch-packages] [Bug 1832659] Re: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832659 Title: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Regression was introduced in OpenSSL 1.1.1 and fixed in 1.1.1b that prevents initialising libcrypto/libssl multiple times, and/or with different options. * This breaks existing applications that correctly use init API, ie. initialise libcrypto before/separately from libssl and/or with different options. [Test Case] * wget https://bugs.launchpad.net/ubuntu/cosmic/+source/openssl/+bug/1832659/+attachment/5270802/+files/test_multiple_libssl_libcrypto_init.py * python3 ./test_multiple_libssl_libcrypto_init.py test_multiple_init (__main__.TestMultipleInit) ... ok -- Ran 1 test in 0.014s OK [Regression Potential] * This is a cherrypick from upstream, and is backwards compatible with existing code. Simply init succeeds under more conditions now, than it did previously in 1.1.1. Also with this fix, OpenSSL is back to how things used to work with 1.1.0 and prior releases. [Original Bug report] After the update of openssl in bionic, I started having an issue and after troubleshooting found this issue: https://github.com/openssl/openssl/issues/7350 Applying the patch linked in that issue and rebuilding the openssl package avoided the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu Jun 13 00:21:16 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1832659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833443] [NEW] Calculator button does nothing (Calculator not launched)
Public bug reported: Troubleshoot steps followed: https://wiki.ubuntu.com/Hotkeys/Troubleshooting. I can try provide info from https://wiki.ubuntu.com/DebuggingProcedures if wanted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.22 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_51_55_generic_52 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.warzone2100.rules 70-snap.core.rules 70-snap.opendungeons.rules 56-hpmud.rules S99-2000S1.rules 70-snap.minetest.rules 40-libsane.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules Date: Wed Jun 19 17:58:19 2019 InstallationDate: Installed on 2019-05-14 (36 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=9b9d08ae-0424-4d09-87e0-5db4115b3a2b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.60 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.60:bd03/12/2015:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833443 Title: Calculator button does nothing (Calculator not launched) Status in systemd package in Ubuntu: New Bug description: Troubleshoot steps followed: https://wiki.ubuntu.com/Hotkeys/Troubleshooting. I can try provide info from https://wiki.ubuntu.com/DebuggingProcedures if wanted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.22 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_51_55_generic_52 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.warzone2100.rules 70-snap.core.rules 70-snap.opendungeons.rules 56-hpmud.rules S99-2000S1.rules 70-snap.minetest.rules 40-libsane.rules 70-snap.canonical-livepatch.rules 70-snap.chromium.rules Date: Wed Jun 19 17:58:19 2019 InstallationDate: Installed on 2019-05-14 (36 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=9b9d08ae-0424-4d09-87e0-5db4115b3a2b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.60 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.60:bd03/12/2015:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Please test proposed package
Hello halfgaar, or anyone else affected, Accepted bash into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bash/4.4.18-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Committed Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications abou
[Touch-packages] [Bug 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Hello halfgaar, or anyone else affected, Accepted bash into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bash/4.4.18-2ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bash (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: bash (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Committed Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indetermina
[Touch-packages] [Bug 1833440] [NEW] My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange
Public bug reported: There is a newer version of libsoup that allows NTLMv2 authentication that resolves this issue. Here is a bug from the Gnome libsoup bug report: https://gitlab.gnome.org/GNOME/libsoup/issues/114 In this bug report for Evolution: https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 someone mentions "the change landed after 2.64.0 and before 2.65.1 and seems to be part of 2.65.1+ only" ** Affects: libsoup2.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1833440 Title: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange Status in libsoup2.4 package in Ubuntu: New Bug description: There is a newer version of libsoup that allows NTLMv2 authentication that resolves this issue. Here is a bug from the Gnome libsoup bug report: https://gitlab.gnome.org/GNOME/libsoup/issues/114 In this bug report for Evolution: https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 someone mentions "the change landed after 2.64.0 and before 2.65.1 and seems to be part of 2.65.1+ only" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1833440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
This update breaks salt-ssh 2016.11.2 (started from a different computer
that's running Debian Stretch) on Ubuntu 18.04 (running on the machine
being managed). Having Salt break from one day to the next for managing
an LTS (!) release is a rather major PITA.
Curiously enough, salt-ssh 2016.11.2 continues to work just fine on
minions running Ubuntu 19.04 which ships openssl 1.1.1b-1ubuntu2.1. So
whatever this SRU does apparently is different from how it works on
Ubuntu 19.04.
This is the error message (from salt-ssh):
=== Begin ===
Traceback (most recent call last):
File "/var/tmp/.root_bdab0e_salt/salt-call", line 15, in
salt_call()
File "/var/tmp/.root_bdab0e_salt/py2/salt/scripts.py", line 374, in
salt_call
import salt.cli.call
File "/var/tmp/.root_bdab0e_salt/py2/salt/cli/call.py", line 9, in
import salt.cli.caller
File "/var/tmp/.root_bdab0e_salt/py2/salt/cli/caller.py", line 18, in
import salt.loader
File "/var/tmp/.root_bdab0e_salt/py2/salt/loader.py", line 29, in
import salt.utils.event
File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/event.py", line 72,
in
import salt.payload
File "/var/tmp/.root_bdab0e_salt/py2/salt/payload.py", line 17, in
import salt.crypt
File "/var/tmp/.root_bdab0e_salt/py2/salt/crypt.py", line 43, in
import salt.utils.rsax931
File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/rsax931.py", line 83,
in
libcrypto = _init_libcrypto()
File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/rsax931.py", line 74,
in _init_libcrypto
raise OSError("Failed to initialize OpenSSL library
(OPENSSL_init_crypto failed)")
OSError: Failed to initialize OpenSSL library (OPENSSL_init_crypto
failed)
=== End ===
I was able to narrow it down to ssl.create_default_context() (invoked by
tornado.netutil which salt-ssh imports indirectly via tornado.iostream)
causing OPENSSL_init_crypto() to return 0 (error) on Ubuntu 18.04, but 1
(success) on Ubuntu 19.04.
=== Begin Ubuntu 18.04 ===
root@bob:~# PYTHONPATH=/var/tmp/.root_bdab0e_salt/py2 python
Python 2.7.15+ (default, Nov 27 2018, 23:36:35)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>> _client_ssl_defaults = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
[ctypes setup for libcrypto]
>>> libcrypto.OPENSSL_init_crypto(OPENSSL_INIT_NO_LOAD_CONFIG |
... OPENSSL_INIT_ADD_ALL_CIPHERS |
... OPENSSL_INIT_ADD_ALL_DIGESTS, None)
0
>>>
=== End Ubuntu 18.04 ===
=== Begin Ubuntu 19.04 ===
root@bob:~# PYTHONPATH=/var/tmp/.root_bdab0e_salt/py2 python
Python 2.7.15+ (default, Nov 27 2018, 23:36:35)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>> _client_ssl_defaults = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
[ctypes setup for libcrypto]
>>> libcrypto.OPENSSL_init_crypto(OPENSSL_INIT_NO_LOAD_CONFIG |
... OPENSSL_INIT_ADD_ALL_CIPHERS |
... OPENSSL_INIT_ADD_ALL_DIGESTS, None)
1
>>>
=== End Ubuntu 19.04 ===
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in libio-socket-ssl-perl source package in Bionic:
Fix Released
Status in libnet-ssleay-perl source package in Bionic:
Fix Released
Status in libwww-perl source package in Bionic:
Fix Released
Status in openssl source package in Bionic:
Fix Released
Status in python-cryptography source package in Bionic:
Fix Released
Status in python-tornado source package in Bionic:
Fix Committed
Status in python2.7 source package in Bionic:
Fix Released
Status in python3.6 source package in Bionic:
Fix Released
Status in python3.7 source package in Bionic:
Fix Released
Status in r-cran-openssl source package in Bionic:
Fix Released
Status in ruby-openssl source package in Bionic:
Fix Released
Status in ruby2.5 source package in Bionic:
Fix Released
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the neg
[Touch-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
Just to add my $.02 . . . I also had this problem with perhaps 6/12 daily and then I zsyncd what I think is the 6/15 daily . . . finding the same "kernel panic" report as Dan found. A couple days later I downloaded a fresh 19.04 iso and ran the install . . . and that went well. Glad to hear that a fix has been engineered, right now I don't have the 19.10 iso installed to flash drive so I can't test out this proposed fix . . . may or may not get to that . . . . I might try to upgrade to 19.10 via the console . . . . But, this problem was "frustrating" in that, as Dan mentions, the "live" system appeared to be "fine" and the installer did not report "errors" and yet would not boot into the installed system, or tty to try stuff out . . . which possibly would have failed anyway?? -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) 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 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I know that if I reinstall from scratch my Kubuntu 18.04, it would fix the issue but it is not acceptable for the reliability of Linux comparing to MacOS or Windows to have to do this. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
This bug was fixed in the package ibus-libpinyin -
1.11.0-1ubuntu0.18.04.1
---
ibus-libpinyin (1.11.0-1ubuntu0.18.04.1) bionic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Wed, 22 May 2019 17:06:00
+0200
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Released
Status in libpinyin source package in Bionic:
Fix Released
Status in ibus-libpinyin source package in Cosmic:
Fix Released
Status in libpinyin source package in Cosmic:
Fix Released
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.04.1
---
libpinyin (2.2.2-1~ubuntu18.04.1) bionic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Mon, 22 May 2019 16:54:00
+0200
** Changed in: ibus-libpinyin (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 libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Released
Status in libpinyin source package in Bionic:
Fix Released
Status in ibus-libpinyin source package in Cosmic:
Fix Released
Status in libpinyin source package in Cosmic:
Fix Released
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
This bug was fixed in the package ibus-libpinyin -
1.11.0-1ubuntu0.18.10.1
---
ibus-libpinyin (1.11.0-1ubuntu0.18.10.1) cosmic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Wed, 22 May 2019 17:06:00
+0200
** Changed in: ibus-libpinyin (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
** Changed in: libpinyin (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 libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Released
Status in libpinyin source package in Bionic:
Fix Released
Status in ibus-libpinyin source package in Cosmic:
Fix Released
Status in libpinyin source package in Cosmic:
Fix Released
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Update Released
The verification of the Stable Release Update for libpinyin 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 libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Released
Status in libpinyin source package in Bionic:
Fix Released
Status in ibus-libpinyin source package in Cosmic:
Fix Released
Status in libpinyin source package in Cosmic:
Fix Released
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.10.1
---
libpinyin (2.2.2-1~ubuntu18.10.1) cosmic; urgency=medium
* Backport of the disco version as an SRU in an attempt to reduce the
number of crashes (LP: #1768166).
-- Gunnar Hjalmarsson Mon, 22 May 2019 16:54:00
+0200
** Changed in: libpinyin (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 libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Released
Status in libpinyin source package in Bionic:
Fix Released
Status in ibus-libpinyin source package in Cosmic:
Fix Released
Status in libpinyin source package in Cosmic:
Fix Released
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833237] Re: skiboot ftbfs in eoan
Launchpad has imported 2 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=24704. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-06-19T12:20:14+00:00 Matthias Klose wrote: This was seen building skiboot 6.2 for powerpc64-linux-gnu using binutils trunk 20190614. (gdb) run Starting program: /usr/bin/powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o Breakpoint 1, _bfd_error_handler (fmt=0x77f6b480 "BFD %s internal error, aborting at %s:%d in %s\n") at ../../bfd/bfd.c:1174 1174../../bfd/bfd.c: No such file or directory. (gdb) bt #0 _bfd_error_handler (fmt=0x77f6b480 "BFD %s internal error, aborting at %s:%d in %s\n") at ../../bfd/bfd.c:1174 #1 0x77ebc6c4 in _bfd_abort (file=file@entry=0x77f7e071 "../../bfd/elf64-ppc.c", line=line@entry=15381, fn=fn@entry=0x77f81480 <__PRETTY_FUNCTION__.18116> "ppc64_elf_relocate_section") at ../../bfd/bfd.c:1440 #2 0x77ee1e70 in ppc64_elf_relocate_section (output_bfd=output_bfd@entry=0x5570b4c0, info=, input_bfd=input_bfd@entry=0x55740d00, input_section=input_section@entry=0x55742270, contents=, relocs=relocs@entry=0x55744ca8, local_syms=, local_sections=) at ../../bfd/elf64-ppc.c:15381 #3 0x77f133e1 in elf_link_input_bfd (flinfo=flinfo@entry=0x7fffe0e0, input_bfd=input_bfd@entry=0x55740d00) at ../../bfd/elflink.c:10887 #4 0x77f14eef in bfd_elf_final_link (abfd=, info=) at ../../bfd/elflink.c:12215 #5 0x55578e0f in ldwrite () at ../../ld/ldwrite.c:581 #6 0x55561514 in main (argc=, argv=) at ../../ld/ldmain.c:457 Reply at: https://bugs.launchpad.net/ubuntu/+source/skiboot/+bug/1833237/comments/1 On 2019-06-19T12:20:44+00:00 Matthias Klose wrote: Created attachment 11848 test case Reply at: https://bugs.launchpad.net/ubuntu/+source/skiboot/+bug/1833237/comments/2 ** Changed in: binutils Status: Unknown => Confirmed ** Changed in: binutils Importance: Unknown => Medium -- 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/1833237 Title: skiboot ftbfs in eoan Status in binutils: Confirmed Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
This feels like enough testing to consider this SRU verified. Thanks
Ping-Wu, thanks Gunnar! Let me release this into -updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Committed
Status in libpinyin source package in Bionic:
Fix Committed
Status in ibus-libpinyin source package in Cosmic:
Fix Committed
Status in libpinyin source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833415] Re: Version.sha256 throws SystemError
In any case, those fields go away today, so the problem will be fixed as well :) - hashes must be used instead, those fields have been deprecated for quite some time already (since 1.1). -- 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/1833415 Title: Version.sha256 throws SystemError Status in python-apt package in Ubuntu: In Progress Bug description: Attempting to access the property raised the exception 'SystemError: error return without exception set' The error occurs when version._records.hashes.file_size == 0. The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS system ; attempting to download the source *deb file failed. Doing an apt-get clean / apt-get update / apt upgrade seemed to make the problem go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 19 08:20:32 2019 InstallationDate: Installed on 2019-06-05 (13 days ago) InstallationMedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1833415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833415] Re: Version.sha256 throws SystemError
OK, so that's a minor issue, yes, it should be raising a nicer error message "No MD5 exists"; but it's really only cosmetic. ** Changed in: python-apt (Ubuntu) Status: New => In Progress ** Changed in: python-apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: python-apt (Ubuntu) Importance: Undecided => Low -- 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/1833415 Title: Version.sha256 throws SystemError Status in python-apt package in Ubuntu: In Progress Bug description: Attempting to access the property raised the exception 'SystemError: error return without exception set' The error occurs when version._records.hashes.file_size == 0. The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS system ; attempting to download the source *deb file failed. Doing an apt-get clean / apt-get update / apt upgrade seemed to make the problem go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 19 08:20:32 2019 InstallationDate: Installed on 2019-06-05 (13 days ago) InstallationMedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1833415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833415] [NEW] Version.sha256 throws SystemError
Public bug reported: Attempting to access the property raised the exception 'SystemError: error return without exception set' The error occurs when version._records.hashes.file_size == 0. The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS system ; attempting to download the source *deb file failed. Doing an apt-get clean / apt-get update / apt upgrade seemed to make the problem go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 19 08:20:32 2019 InstallationDate: Installed on 2019-06-05 (13 days ago) InstallationMedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot showing object state in PyCharm debugger" https://bugs.launchpad.net/bugs/1833415/+attachment/5271571/+files/badhash.png -- 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/1833415 Title: Version.sha256 throws SystemError Status in python-apt package in Ubuntu: New Bug description: Attempting to access the property raised the exception 'SystemError: error return without exception set' The error occurs when version._records.hashes.file_size == 0. The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS system ; attempting to download the source *deb file failed. Doing an apt-get clean / apt-get update / apt upgrade seemed to make the problem go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 19 08:20:32 2019 InstallationDate: Installed on 2019-06-05 (13 days ago) InstallationMedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1833415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
** Changed in: binutils (Ubuntu) Status: New => Fix Released ** Changed in: eclipse-titan (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7 (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7-cross (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7-cross-ports (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8 (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8-cross (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8-cross-ports (Ubuntu) Status: New => Fix Released ** Changed in: gcc-defaults (Ubuntu) Status: New => Fix Released ** Changed in: gcc-defaults-ports (Ubuntu) Status: New => Fix Released ** Changed in: ggcov (Ubuntu) Status: New => 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/1828171 Title: New toolchain updates need to be rebuilt against -security only Status in binutils package in Ubuntu: Fix Released Status in eclipse-titan package in Ubuntu: Fix Released Status in gcc-7 package in Ubuntu: Fix Released Status in gcc-7-cross package in Ubuntu: Fix Released Status in gcc-7-cross-ports package in Ubuntu: Fix Released Status in gcc-8 package in Ubuntu: Fix Released Status in gcc-8-cross package in Ubuntu: Fix Released Status in gcc-8-cross-ports package in Ubuntu: Fix Released Status in gcc-defaults package in Ubuntu: Fix Released Status in gcc-defaults-ports package in Ubuntu: Fix Released Status in ggcov package in Ubuntu: Fix Released Status in binutils source package in Bionic: Fix Released Status in eclipse-titan source package in Bionic: Fix Released Status in gcc-7 source package in Bionic: Fix Released Status in gcc-7-cross source package in Bionic: Fix Released Status in gcc-7-cross-ports source package in Bionic: Fix Released Status in gcc-8 source package in Bionic: Fix Released Status in gcc-8-cross source package in Bionic: Fix Released Status in gcc-8-cross-ports source package in Bionic: Fix Released Status in gcc-defaults source package in Bionic: Fix Released Status in gcc-defaults-ports source package in Bionic: Fix Released Status in ggcov source package in Bionic: Fix Released Status in binutils source package in Cosmic: Fix Released Status in eclipse-titan source package in Cosmic: Fix Released Status in gcc-7 source package in Cosmic: Fix Released Status in gcc-7-cross source package in Cosmic: Fix Released Status in gcc-7-cross-ports source package in Cosmic: Fix Released Status in gcc-8 source package in Cosmic: Fix Released Status in gcc-8-cross source package in Cosmic: Fix Released Status in gcc-8-cross-ports source package in Cosmic: Fix Released Status in gcc-defaults source package in Cosmic: Fix Released Status in gcc-defaults-ports source package in Cosmic: Fix Released Status in ggcov source package in Cosmic: Fix Released Bug description: [Impact] With LP: #1814369, the toolchain packages have been updated in both cosmic and bionic, but due to an error those packages were built in -proposed as any regular SRU. For toolchain updates there exists a policy that those should be always built against -security *only*, and then released to both -security and -updates. Since this is not the case with the current toolchain update, we need to no-change rebuild all of the previously released toolchain packages in a -security enabled devirt PPA, sync them to -proposed with binaries and then release into the archives. [Regression Potential] As these are toolchain packages, there is always some regression potential. These will be no-change rebuilds so in theory the risk should be low, but the current versions of the packages have not been built against -security only before. It is hard to say how any regressions could manifest themselves. [Test Case] Making sure there are no reported regressions in the GCC and binutils test suites. Hopefully this will be sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: binutils (Ubuntu) Status: New => 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: Fix Released 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 1833237] Re: skiboot ftbfs in eoan
** Bug watch added: Sourceware.org Bugzilla #24704 https://sourceware.org/bugzilla/show_bug.cgi?id=24704 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=24704 Importance: Unknown Status: Unknown -- 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/1833237 Title: skiboot ftbfs in eoan Status in binutils: Unknown Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
It is not fixed in 18.04. My Kubuntu 18.04 worked with no sound issue up to mid may 2019. One morning, no longer sound ! I have tested all the solution proposed with no success... I think It Would be useful to create another bug linked to 18.04 LTS. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
I modified libxrandr to return the actual error code returned from XRRSetCrtcConfig(): --- libxrandr-1.5.1.orig/src/XrrCrtc.c +++ libxrandr-1.5.1/src/XrrCrtc.c @@ -155,9 +155,10 @@ XRRSetCrtcConfig (Display *dpy, req->mode = mode; req->rotation = rotation; Data32 (dpy, outputs, noutputs << 2); +int ret_code = _XReply (dpy, (xReply *) &rep, 0, xFalse); +if (ret_code != 0) +rep.status = ret_code; -if (!_XReply (dpy, (xReply *) &rep, 0, xFalse)) - rep.status = RRSetConfigFailed; UnlockDisplay (dpy); SyncHandle (); return rep.status; And it shows: xfce4-settings(displays): Configuring CRTC 79. xfce4-settings(displays): Applying changes to CRTC 79. xfce4-settings(displays): Applying CRTC 79 Transform: x=0.00 y=0.00, filter=bilinear. (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.650: XRRSetCrtcConfig()=1, sleeping (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.655: XRRSetCrtcConfig()=1, sleeping (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.657: XRRSetCrtcConfig()=1, sleeping (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.658: XRRSetCrtcConfig()=1, sleeping (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.660: XRRSetCrtcConfig()=1, sleeping (xfsettingsd:7726): xfsettingsd-WARNING **: 12:44:13.661: Failed to configure CRTC 79 XRRSetCrtcConfig()=1. xfce4-settings(displays): Configuring CRTC 80. (xfsettingsd:7726): xfsettingsd-CRITICAL **: 12:44:13.662: Failed to apply display settings xfce4-settings(displays): RRScreenChangeNotify event received. -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
I have tested this patch in virtualbox and it works for me. -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) 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 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781699] Re: DHCPv6 server crashes regularly (bionic)
** Changed in: isc-dhcp (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in DHCP: Unknown Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Bionic: Fix Released Status in isc-dhcp source package in Cosmic: Fix Released Status in isc-dhcp source package in Disco: Fix Released Status in isc-dhcp source package in Eoan: Fix Released Status in isc-dhcp package in Debian: Fix Released Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1781699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768166] Re: Random crashes
Thanks Ping-Wu!
Our attempts to recruit additional Chinese testers failed unfortunately.
My view is that we still are ready to consider the proposed packages
verified. I base my view on:
* The bug reporter's test results according to comment #35
* My own verification measures according to comment #23
* The reporter of bug #1829947 expressed a positive testimony as to
the ibus-libpinyin version we are backporting here (comment #20 in
that report).
* The proposed packages have 'matured' in -proposed for soon three
weeks.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
Status in ibus-libpinyin package in Ubuntu:
Fix Released
Status in libpinyin package in Ubuntu:
Fix Released
Status in ibus-libpinyin source package in Bionic:
Fix Committed
Status in libpinyin source package in Bionic:
Fix Committed
Status in ibus-libpinyin source package in Cosmic:
Fix Committed
Status in libpinyin source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ibus-libpinyin has proved to crash far too often. One or more files in
~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
directory allows the user to keep using ibus-libpinyin.
In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
present, and the number of crashes has been reduced significantly:
https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
Upstream ChangeLog ibus-libpinyin:
--
version 1.11.0
* fixes keypad decimal
* fixes emoji candidates
* support configurable opencc config
version 1.10.92
* fixes Enter handling
version 1.10.91
* support ime.register_trigger in lua extension
* support predicted candidates
* support emoji input
version 1.10.0
* bug fixes
version 1.9.91
* migrate to use GSettings
* fixes lyx short cut issue
version 1.9.3
* translate input method name in ibus menu
Upstream ChangeLog libpinyin:
-
version 2.2.2
* minor fixes
version 2.2.1
* fixes predicted candidates
version 2.2.0
* bug fixes
The proposal is to backport the disco versions of those packages to
bionic and cosmic in an attempt to prevent crashes. Proposed uploads
are available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
[Test Case]
* Install from {bionic,cosmic}-proposed:
- libpinyin13
- libpinyin-data
- ibus-libpinyin
* Use "Intelligent Pinyin" for typing and confirm that no new issues
show up when doing so.
(This is apparently not a confirmation that the upload really fixes
the bug. To compensate for that, we will await testing of the
-proposed packages by a few Chinese users before considering the
uploads verified.)
Reverse dependencies
Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on
packages belonging to the libpinyin source package. So additional test measures
are:
* Install fcitx-libpinyin and ibus-libzhuyin.
* Use both those tools for typing Chinese, and confirm that you don't
observe any adverse effects of the libpinyin upgrade.
[Regression Potential]
The changes are mostly bug fixes, so the regression risk should be
limited. Also consider that the starting point is a rather unstable
functionality.
NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
as much testing as possible. There do not seem to be too many risky
changes carried, but such jumps in upstream versions always carry some
regression-risk.
[Original description]
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the
Ubuntu Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
Similar issue was just fixed in ubuntu-release-upgrader (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1727472). It would be great if the issue could be fixed in python-apt as well. -- 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/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833198] Re: CURL shipped with Ubuntu 18.04 contained bug #2303
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1833198 Title: CURL shipped with Ubuntu 18.04 contained bug #2303 Status in curl package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 lsb_release -rd Description: Ubuntu 18.04.2 LTS ships with cURL version ... apt-cache policy curl curl: Installed: 7.58.0-2ubuntu3.7 Candidate: 7.58.0-2ubuntu3.7 Version table: *** 7.58.0-2ubuntu3.7 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 7.58.0-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages which contains bug #2303 https://github.com/curl/curl/issues/2303 The Ubuntu package needs to updated to take a version that contains a fix for this bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1833198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830146] Re: Checkbox detect an extra webcam "video1"
@Sylvain CID: 201711-25942 Video devices information as attached. ** Attachment added: "videos_info.txt" https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+attachment/5271560/+files/videos_info.txt -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Provider for Plainbox - Checkbox: Confirmed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833198] Re: CURL shipped with Ubuntu 18.04 contained bug #2303
** Package changed: hdf5 (Ubuntu) => curl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1833198 Title: CURL shipped with Ubuntu 18.04 contained bug #2303 Status in curl package in Ubuntu: New Bug description: Ubuntu 18.04 lsb_release -rd Description: Ubuntu 18.04.2 LTS ships with cURL version ... apt-cache policy curl curl: Installed: 7.58.0-2ubuntu3.7 Candidate: 7.58.0-2ubuntu3.7 Version table: *** 7.58.0-2ubuntu3.7 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 7.58.0-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages which contains bug #2303 https://github.com/curl/curl/issues/2303 The Ubuntu package needs to updated to take a version that contains a fix for this bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1833198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833198] [NEW] CURL shipped with Ubuntu 18.04 contained bug #2303
You have been subscribed to a public bug: Ubuntu 18.04 lsb_release -rd Description:Ubuntu 18.04.2 LTS ships with cURL version ... apt-cache policy curl curl: Installed: 7.58.0-2ubuntu3.7 Candidate: 7.58.0-2ubuntu3.7 Version table: *** 7.58.0-2ubuntu3.7 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 7.58.0-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages which contains bug #2303 https://github.com/curl/curl/issues/2303 The Ubuntu package needs to updated to take a version that contains a fix for this bug ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- CURL shipped with Ubuntu 18.04 contained bug #2303 https://bugs.launchpad.net/bugs/1833198 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-06-19 03:47 EDT--- IBM Bugzilla status -> closed, Will not be fixed by Canonical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Won't Fix Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets activated
[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Triaged Bug description: https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 --- Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Triaged Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1663528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
** Changed in: lvm2 Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount Status in lvm2: New Status in libvirt package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New Bug description: When using automatic suspend at reboot/shutdown, it makes sense to store the suspend data on a separate partition to ensure there is always enough available space. However this does not work, as the partition gets unmounted before or during libvirt suspend. Steps to reproduce: 1. Use Ubuntu 18.04.02 LTS 2. Install libvirt + qemu-kvm 3. Start a guest 4. Set libvirt-guests to suspend at shutdown/reboot by editing /etc/default/libvirt-guests 5. Create a fstab entry to mount a separate partition to mount point /var/lib/libvirt/qemu/save. Then run sudo mount /var/lib/libvirt/qemu/save to mount the partition. 6. Reboot Expected result: The guest suspend data would be written to the /var/lib/libvirt/qemu/save, resulting in the data being stored at the partition specified in fstab. At boot, this partition would be mounted as specified in fstab and libvirt-guest would be able to read the data and restore the guests. Actual result: The partition gets unmounted before libvirt-guests suspends the guests, resulting in the data being stored on the partition containing the root file system. During boot, the empty partition gets mounted over the non-empty /var/lib/libvirt/qemu/save directory, resulting in libvirt-guests being unable to read the saved data. As a side effect, the saved data is using up space on the root partition even if the directory appears empty. Here is some of the relevant lines from the journal: Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: Deactivating block devices: Jun 14 00:00:04 libvirt-host systemd[1]: Unmounted /var/lib/libvirt/qemu/save. Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [UMOUNT]: unmounting libvirt_lvm-suspenddata (dm-3) mounted on /var/lib/libvirt/qemu/save... done Jun 14 00:00:04 libvirt-host libvirt-guests.sh[4349]: Running guests on default URI: vps1, vps2, vps3 Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [MD]: deactivating raid1 device md1... done Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending guests on default URI... Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:05 libvirt-host blkdeactivate[4343]: [LVM]: deactivating Volume Group libvirt_lvm... skipping Jun 14 00:00:10 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: 5.989 GiB Jun 14 00:00:15 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:20 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1832859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4
It's there now. The sync must have failed. -- 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/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Disco: In Progress Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do not release readonly property” to glib-2-60 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to glib-2-60 * Translation updates: - Catalan Overview of changes in GLib 2.60.1 == * Fix documentation for `gdbus-tool wait` to use correct units * Bugs fixed: - #1709 GResource generation test incompatible with stable LLVM on Linux - #1725 gosxappinfo.h is not installed on macOS - #1737 gdbus-tool wait command timeout argument incorrect unit reference - !711 socket: Fix annotation for flags in g_socket_receive_message - !722 Backport codegen: Fix use of uninitialised variable from !721 to glib-2-60 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” to glib-2-60 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” to glib-2-60 - !758 gdbusaddress, win32: backport using cwd for running rundll32 - !775 meson: Hotfix for iconv detection on macOS * Translation updates: - Basque - Dutch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4
It was clear that the sync was what I was going for (comment #1), so it would have been nice if the SRU would have been accepted by the way. Brian could have synced it if necessary as well. Now we have to wait for another go-round. -- 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/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Disco: In Progress Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do not release readonly property” to glib-2-60 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to glib-2-60 * Translation updates: - Catalan Overview of changes in GLib 2.60.1 == * Fix documentation for `gdbus-tool wait` to use correct units * Bugs fixed: - #1709 GResource generation test incompatible with stable LLVM on Linux - #1725 gosxappinfo.h is not installed on macOS - #1737 gdbus-tool wait command timeout argument incorrect unit reference - !711 socket: Fix annotation for flags in g_socket_receive_message - !722 Backport codegen: Fix use of uninitialised variable from !721 to glib-2-60 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” to glib-2-60 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” to glib-2-60 - !758 gdbusaddress, win32: backport using cwd for running rundll32 - !775 meson: Hotfix for iconv detection on macOS * Translation updates: - Basque - Dutch To manage notifications about this bug go to: https://bugs.launchpad.net/
[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack
autopkgtests cleared ** Changed in: mesa (Ubuntu Bionic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
