[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
I have asked you not to modify the state of these bug tasks, which are used by the developers to track the progress on this fix. ** Changed in: base-files (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: Fix Committed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu Xenial) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu Xenial) Assignee: shane cody perry (theinsanelunatic5934) => (unassigned) ** Changed in: base-files (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836290] Re: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed
** Summary changed: - gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. + gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. -- 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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed.
** Summary changed: - /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. + gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. ** Tags added: nouveau ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu Xenial) Status: Fix Committed => New ** Changed in: base-files (Ubuntu Xenial) Assignee: (unassigned) => shane cody perry (theinsanelunatic5934) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637800] Autopkgtest regression report (base-files/9.4ubuntu4.9)
All autopkgtests for the newly accepted base-files (9.4ubuntu4.9) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Hello Alexandre, or anyone else affected, Accepted base-files into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/9.4ubuntu4.10 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: base-files (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: Fix Committed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
This bug was fixed in the package ibus - 1.5.19-4ubuntu2 --- ibus (1.5.19-4ubuntu2) eoan; urgency=medium * debian/patches/git-support-common_name-in-ISO-639.patch: - Use "Bangla" instead of "Bengali" when labeling bn IBus input methods for the UIs (LP: #991002). -- Gunnar Hjalmarsson Wed, 10 Jul 2019 18:46:00 +0200 ** Changed in: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn Status in CLDR: Fix Released Status in GLibC: Fix Released Status in gnome-desktop: New Status in ibus: Fix Released Status in xkeyboard-config: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in iso-codes package in Ubuntu: Fix Released Status in langpack-locales package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in localechooser package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in iso-codes package in Debian: Fix Released Status in xkeyboard-config package in Debian: Fix Released Bug description: The official name for the state language for Bangladesh is Bangla, as detailed on section 3, part 1 of the Bangladesh constitution (http://www1.umn.edu/humanrts/research/bangladesh-constitution.pdf). However, language selector continues to refer to this language as Bengali (Bangladeh). While Bengali has been historically used as the english name for the language during colonial periods, the name 'Bangla' is more widely used nowadays. It is also the name with which native speakers identify the language. This package uses Bengali(Bangladesh) as the identifier for language code bn-BD. Please change the name to Bangla(Bangladesh). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: language-selector-gnome 0.79 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 29 16:14:25 2012 PackageArchitecture: all ProcEnviron: LANGUAGE=bn_BD:bn:en_IN:en_GB:en PATH=(custom, no user) LANG=bn_BD.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to precise on 2012-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Please do not change the triage state of these bug tasks. ** Changed in: base-files (Ubuntu) Status: New => Invalid ** Changed in: base-files (Ubuntu Xenial) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: base-files (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: Fix Released Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836266] Re: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python
you have a locally installed python: Setting up python-minimal (2.7.15~rc1-1) ... Traceback (most recent call last): File "/usr/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/local/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/local/lib/python2.7/compileall.py", line 16, in import struct File "/usr/local/lib/python2.7/struct.py", line 1, in from _struct import * ImportError: No module named _struct dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python-minimal dpkg: regarding .../python_2.7.15~rc1-1_amd64.deb containing python, pre-dependency problem: python pre-depends on python-minimal (= 2.7.15~rc1-1) python-minimal latest configured version is 2.7.11-1. dpkg: error processing archive /var/cache/apt/archives/python_2.7.15~rc1-1_amd64.deb (--unpack): pre-dependency problem - not installing python -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1836266 Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python Status in python-defaults package in Ubuntu: Incomplete Bug description: I tried to upgrade ubuntu and cath whis bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python 2.7.11-1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jul 12 01:04:31 2019 ErrorMessage: pre-dependency problem - not installing python InstallationDate: Installed on 2017-08-27 (683 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python-defaults Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1836266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836279] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
*** This bug is a duplicate of bug 1836236 *** https://bugs.launchpad.net/bugs/1836236 ** This bug has been marked a duplicate of bug 1836236 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836279 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: New Bug description: terying to upgrade from 1404 to 1604 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jul 11 16:47:21 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2013-07-04 (2198 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
This bug was fixed in the package unattended-upgrades - 1.13 --- unattended-upgrades (1.13) unstable; urgency=medium [ Alban VIDAL ] * Update french translation. Signed-off-by: Alban VIDAL [ Balint Reczey ] * Don't crash collecting transitive dependencies when package has no candidate (LP: #1825886) * Use mark_install_adjusted() in rewind_cache() The original cache had packages marked with adjustments thus rewinding should also do adjustments to reach the same state. Not using mark_install_adjusted() also crashes when apt raises error on held packages. (LP: #1826157) * test_rewind: Update test to check if adjustend rewinding took place * Only allow removals in valid autoremoval sets * Fix one more log location in the man page (Closes: #928601) * Factor out kernel regexp generation to functions * Packages including kernel version without flavor in their name may be kernel packages. Also add autopkgtest for checking if the generated patterns cover the currently running kernel. (LP: #1828200) * Skip upgrade-all-security test when there are no updates to test with. Shortly after a release there may not be security updates against the packages used in the chroot used for the test. * Test with latest stable in upgrade-all-security on testing * Fix testing Debian's updates in upgrade-all-security * Store list of kept packages and report the number of them in motd (LP: #1823070) * Mention APT's apt-daily-upgrade.service in the man page * 50unattended-upgrades.md5sum add MD5 of current files * PEP8: Fix breaking line after binary operator * debian/tests/control: Fix Depends: of upgrade-between-snapshots * debian/tests/control: Allow stderr in kernel-patterns [ Gordon Lack ] * Replace boolean Unattended-Upgrade::MailOnlyOnError2 mail reporting setting with multi-valued (string) Unattended-Upgrade::MailReport. [ Jaime Hablutzel ] * Error message improved on very improbable condition [ Clint Armstrong ] * Fix showing multi-line strings on Plymouth. When unattended-upgrades sends it's status to plymouth it sends a multi-line string which causes plymouth to display overlapping text, because plymouth only scrolls one line when the message is sent. (LP: 1826406) -- Balint Reczey Mon, 08 Jul 2019 11:08:30 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828200] Re: [SRU] kernel package names ending with version without flavor are not matched by generated patterns
This bug was fixed in the package unattended-upgrades - 1.13 --- unattended-upgrades (1.13) unstable; urgency=medium [ Alban VIDAL ] * Update french translation. Signed-off-by: Alban VIDAL [ Balint Reczey ] * Don't crash collecting transitive dependencies when package has no candidate (LP: #1825886) * Use mark_install_adjusted() in rewind_cache() The original cache had packages marked with adjustments thus rewinding should also do adjustments to reach the same state. Not using mark_install_adjusted() also crashes when apt raises error on held packages. (LP: #1826157) * test_rewind: Update test to check if adjustend rewinding took place * Only allow removals in valid autoremoval sets * Fix one more log location in the man page (Closes: #928601) * Factor out kernel regexp generation to functions * Packages including kernel version without flavor in their name may be kernel packages. Also add autopkgtest for checking if the generated patterns cover the currently running kernel. (LP: #1828200) * Skip upgrade-all-security test when there are no updates to test with. Shortly after a release there may not be security updates against the packages used in the chroot used for the test. * Test with latest stable in upgrade-all-security on testing * Fix testing Debian's updates in upgrade-all-security * Store list of kept packages and report the number of them in motd (LP: #1823070) * Mention APT's apt-daily-upgrade.service in the man page * 50unattended-upgrades.md5sum add MD5 of current files * PEP8: Fix breaking line after binary operator * debian/tests/control: Fix Depends: of upgrade-between-snapshots * debian/tests/control: Allow stderr in kernel-patterns [ Gordon Lack ] * Replace boolean Unattended-Upgrade::MailOnlyOnError2 mail reporting setting with multi-valued (string) Unattended-Upgrade::MailReport. [ Jaime Hablutzel ] * Error message improved on very improbable condition [ Clint Armstrong ] * Fix showing multi-line strings on Plymouth. When unattended-upgrades sends it's status to plymouth it sends a multi-line string which causes plymouth to display overlapping text, because plymouth only scrolls one line when the message is sent. (LP: 1826406) -- Balint Reczey Mon, 08 Jul 2019 11:08:30 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1828200 Title: [SRU] kernel package names ending with version without flavor are not matched by generated patterns Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Apt ships VersionedKernelPackages regex patterns in /etc/apt/apt.conf.d/01autoremove from which /etc/kernel/postinst.d /apt-auto-removal generates kernel package name patterns by appending the running kernel version including the flavor like linux-.*-4.15.0-1010-kvm but those generated patterns don't cover versioned kernel package names including the version without the flavor, such as linux-kvm-tools-4.15.0-1012. Unattended-upgrades generates the patterns in a similar way and also don't cover linux-kvm-tools-4.15.0-1012 and similar packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1828200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830867] Re: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836279] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836279 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: New Bug description: terying to upgrade from 1404 to 1604 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jul 11 16:47:21 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2013-07-04 (2198 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836279] [NEW] package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: terying to upgrade from 1404 to 1604 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jul 11 16:47:21 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2013-07-04 (2198 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-12 (0 days ago) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836279 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: New Bug description: terying to upgrade from 1404 to 1604 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jul 11 16:47:21 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2013-07-04 (2198 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu) Status: In Progress => Invalid ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Changed in: base-files (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836274] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
*** This bug is a duplicate of bug 1836236 *** https://bugs.launchpad.net/bugs/1836236 ** This bug has been marked a duplicate of bug 1836236 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836274 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Bug appeared after upgrading from Ubuntu 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: base-files: Install base-files: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 11 19:01:22 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-19 (1086 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836274] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836274 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Bug appeared after upgrading from Ubuntu 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: base-files: Install base-files: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 11 19:01:22 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-19 (1086 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836274] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836274 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Bug appeared after upgrading from Ubuntu 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: base-files: Install base-files: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 11 19:01:22 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-19 (1086 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836274] [NEW] package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: Bug appeared after upgrading from Ubuntu 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: base-files: Install base-files: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 11 19:01:22 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-19 (1086 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-10 (1 days ago) ** Affects: base-files (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836274 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Bug appeared after upgrading from Ubuntu 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: base-files: Install base-files: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jul 11 19:01:22 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-19 (1086 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2019-07-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
I have the same problem, input crackling, output ok. My setup: ASUS PRIME X470-PRO (ALC1220, latest bios 5007), Ryzen 2700X, 32GB ECC RAM, Kernel 4.19.58. This is really annoying, I'm using a USB dongle for mic input as workaround, but the SNR is not as good as the onboard audio. Tried to fiddle with ALSA kernel module param and pulse audio param, without success. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Well, another update that probably will be the last one from me, since I'm beginning to really hate ALSA. Decided today to try to test some parameters; I had left the audio card loaded with VFIO module since the command dump. Today I've decided to retry to use it, so I've removed the VFIO stubs from modprobe, rebooted and... no PCI audio card. Disabled IOMMU to force load the modules (something like this was already seen by me; even when VFIO wasn't asked to bind it, it would bind it anyway), no PCI audio card. lsmod says that the module is loaded on the audio card, however no audio from any PCI devices, even the audio from the GPU. I'll attach alsa-info. Just for reference on your list, when the module was working, I had output working fine, but input crackling. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Created attachment 283619 alsa-info now completely ignores my PCI audio cards -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Same here. Running on Asus Rog Strix b350-f Gaming. OS: Ubuntu 19.04 - Kernel 5.0.20 - Gnome 3.32 Noticed that when I use Xorg, my input from webcam works out of the box on discord. Now on wayland I need to set tsched=0. Looking at the syslog says that discord was trying to use 48kHz instead of the default 44.1kHz. Already tryied to set "alternative frequency" to 44.1kHz like the default frequency, without success. Now using a usb audio to workaround. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Created attachment 283631 alsa-info on MSI X370 Krait Gaming (MS-7A33) Adding alsa-info, same problem as everyone else - playback is perfect, mic recording crackles. This seems like a rather popular chipset, are we all gonna have to buy USB dongles?! -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
After purging VFIO finally the PCI audio cards works again even after reenabling it. However now from the front panel only the right channel works from the front jack, from the back both works correctly. I don't really understand anything now; nor what the problem is. I'll try to replay some interesting commands from the decoded win dump, hoping for the best; however with all this random problems popping up, I'll really doubt that I will be able to fix anything. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Tried everything, including downgrade to a previous kernel, same behavior. The only thing I get in dmesg now is: [3.146686] hdaudio hdaudioC0D0: Unable to bind the codec [3.150739] hdaudio hdaudioC1D0: Unable to bind the codec Really useful. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Same Bug on Manjaro with kernel 5.2 and the MSI X370 Titanium / ALC1220 -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836266] Re: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot currently work on this bug currently because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also provide the output for the following commands "apt-cache policy python python3 libpython2.7-minimal; python --version; python3 --version" You are running a EOL & unsupported kernel (17.10/4.13) and I see many packages not intended for Xenial (16.04). I suspect it's not a bug, but a 'frakensystem' that has packages intended for other releases (17.10 & 18.04) added which I believe have created your issue. More description of what you were trying to do, behavior expected may have helped. Thank you for taking the time to report this bug and helping to make Ubuntu better. ** Changed in: python-defaults (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1836266 Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python Status in python-defaults package in Ubuntu: Incomplete Bug description: I tried to upgrade ubuntu and cath whis bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python 2.7.11-1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jul 12 01:04:31 2019 ErrorMessage: pre-dependency problem - not installing python InstallationDate: Installed on 2017-08-27 (683 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python-defaults Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1836266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836266] Re: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1836266 Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python Status in python-defaults package in Ubuntu: New Bug description: I tried to upgrade ubuntu and cath whis bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python 2.7.11-1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jul 12 01:04:31 2019 ErrorMessage: pre-dependency problem - not installing python InstallationDate: Installed on 2017-08-27 (683 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python-defaults Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1836266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836266] [NEW] package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python
Public bug reported: I tried to upgrade ubuntu and cath whis bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python 2.7.11-1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jul 12 01:04:31 2019 ErrorMessage: pre-dependency problem - not installing python InstallationDate: Installed on 2017-08-27 (683 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python-defaults Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1836266 Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python Status in python-defaults package in Ubuntu: New Bug description: I tried to upgrade ubuntu and cath whis bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python 2.7.11-1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jul 12 01:04:31 2019 ErrorMessage: pre-dependency problem - not installing python InstallationDate: Installed on 2017-08-27 (683 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python-defaults Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1836266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] [NEW] Update hyperlink when enabling UCA
Public bug reported: When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: New Bug description: When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
This command was reported to successfully work around this bug: sudo sed -i 's/^Automatically/# Automatically/g' /var/lib/dpkg/info /base-files.postinst It changes any lines starting with "Automatically" into comments, which lets the script finish properly when you run: sudo dpkg --configure base-files Or just run this afterwards: sudo apt -f install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
Also facing same issue and downgrading to 18.0.0~rc5-1ubuntu1 version works fine locally. However for heroku hosting (heroku-18 stack), specifying 18.0.0~rc5-1ubuntu1 release in Aptfile doesn't install correctly. -- 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/1835922 Title: missing gl* symbols in version 19.0.2 Status in mesa package in Ubuntu: Confirmed Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned int, unsigned int, unsigned int,
[Touch-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1835922 Title: missing gl* symbols in version 19.0.2 Status in mesa package in Ubuntu: Confirmed Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned int, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x7c5): undefined reference to
[Touch-packages] [Bug 1584386] Re: Main monitor doesn't wake up after system suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1584386 Title: Main monitor doesn't wake up after system suspend Status in xorg package in Ubuntu: Confirmed Bug description: If I lock my Unity session (Super+L) and power down my two monitors using external power switch, when after a few minutes I restore the power to monitors and wake up Ubuntu only my VGA connected LG display wakes up. My main monitor - a DisplayPort connected Dell U2410 wakes up only for a brief moment (it's power led goes blue from yellow) but before any picture would be displayed it goes back to sleep mode (led goes yellow again). All of this is true only for X session. If I switch to tty1 (Ctrl+Alt+F1) the Dell wakes up correctly and shows tty1. Going back to X (Ctrl+Alt+F7) causes this monitor to go to power save mode again. The only means for me to get my main display back in X is to restart the computer, as logging in and out of X doesn't help. I have also tried running Displays configuration tool while in X, but what it only does is that once I click "Detect Displays" button Dell's power led goes blue for a brief moment and then immediately back to yellow (power save mode). I haven't encountered such behavior with Ubuntu 14.04, nor have I experienced right after migrating to 16.04. I believe this regression showed up with some update within the last two weeks. Both monitors are hooked up to AMD Radeon 5850 graphics card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems Ubuntu_Root: clean, 690241/3670016 files, 6292028/14652416 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 21 21:22:43 2016 DistUpgraded: 2016-04-23 22:19:53,020 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] [1002:6899] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] [1002:0b00] InstallationDate: Installed on 2015-08-22 (272 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=a709e3c2-0c9b-4102-8135-3a38cc17bd0b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (27 days ago) dmi.bios.date: 08/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P55-GD65 (MS-7583) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd08/18/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7583:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP55-GD65(MS-7583):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7583 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 21 20:49:42 2016 xserver.configfile: default xserver.errors:
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Tags added: regression-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: New Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
The 2.7 and 3.5 python packages in the security proposed PPA have been successfully tested in a fips and non-fips xenial environment. -- 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/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Status in python3.5 package in Ubuntu: Invalid Status in python2.7 source package in Xenial: In Progress Status in python3.5 source package in Xenial: In Progress Status in python2.7 source package in Bionic: In Progress Status in python3.5 source package in Bionic: Invalid Status in python2.7 source package in Cosmic: Won't Fix Status in python3.5 source package in Cosmic: Invalid Status in python2.7 source package in Disco: In Progress Status in python3.5 source package in Disco: Invalid Status in python2.7 source package in Eoan: Triaged Status in python3.5 source package in Eoan: Invalid Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836236] [NEW] 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Public bug reported: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Description changed: - Trying to install this on xenial result in: + Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): - subprocess installed post-installation script returned error exit status 127 + subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: - base-files + base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? ** Description changed: Trying to install this on xenial results in: + Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) - Because there is a missing comment "#" at the beginning of line 131 of - /var/lib/dpkg/info/base-files.postinst, ie: + + Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: New Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637800] Autopkgtest regression report (base-files/9.4ubuntu4.9)
All autopkgtests for the newly accepted base-files (9.4ubuntu4.9) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Autopkgtest regression report (base-files/10.1ubuntu2.5)
All autopkgtests for the newly accepted base-files (10.1ubuntu2.5) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
For the record our plan is to backport the trigger processing fixes and that work is being tracked in bug 1828639. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
Just to confirm, you mean that this message is shown on the otherwise- blank console when booting with 'quiet'? ** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu) -- 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/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637800] Re: add a motd script for news
Note: during verification, it would be good to also run the test case from LP: #1829968. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637800] Re: add a motd script for news
Hello Dustin, or anyone else affected, Accepted base-files into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/9.4ubuntu4.9 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: base-files (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
** Also affects: systemd (Ubuntu Eoan) Importance: High Assignee: Balint Reczey (rbalint) Status: In Progress -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825981] Re: /usr/lib/tracker/tracker-extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825981 Title: /usr/lib/tracker/tracker- extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload Status in tracker package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker. This problem was most recently seen with package version 2.1.6-1, the problem page at https://errors.ubuntu.com/problem/b99e01aacdc0c848c2170270ddbb577546a03a73 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748956] Re: replace uses of net-tools with iproute2
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1748956 Title: replace uses of net-tools with iproute2 Status in byobu: Fix Committed Status in Release Notes for Ubuntu: Confirmed Status in byobu package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: As ubuntu goes forward, net-tools is looking to be dropped. Byobu currently depends on net-tools. That code should be replaced by iproute2. Related bugs: * bug 925145: cloud-init Use ip instead of ifconfig and route ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: byobu 5.124-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 13:34:27 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (935 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: byobu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/byobu/+bug/1748956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
** Also affects: software-properties (Ubuntu Eoan) Importance: High Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: New Status in software-properties source package in Eoan: New Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836219] [NEW] pidfile_close prevents pidfile_remove from working
Public bug reported:
The whole pidfile_xxx suite, besides being unnecessarily complicated
compared to 1 function in NetBSD, does not do what it says on the tin.
Complications. 4 functions instead of one. pidfile_open requires
pidptr, but doesn't use it. The other functions require an argument
that the documentation says isn't needed, but is.
Error. Most important, pidfile_close modifies its argument such that
pidfile_remove can't use it: both the file descriptor and the name are
destroyed.
The following program and associated output illustrates the problem.
#include
#include
#include
#include
void
show_pfh( const char func[], struct pidfh * pfh ) {
printf( "%s: fh = %d, name = %s\n", func, pfh->pf_fd, pfh->pf_path );
}
int
main(int argc, char *argv[])
{
pid_t pid;
struct pidfh * pfh = pidfile_open("/tmp/foo.pid", 0644, );
if( !pfh ) {
err(EXIT_FAILURE, "pidfile_open");
}
show_pfh("open", pfh);
if( -1 == pidfile_write(pfh) ) {
err(EXIT_FAILURE, "pidfile_write");
}
show_pfh("write", pfh);
if( -1 == pidfile_close(pfh) ) {
err(EXIT_FAILURE, "pidfile_close");
}
show_pfh("close", pfh);
if( -1 == pidfile_remove(pfh) ) {
err(EXIT_FAILURE, "pidfile_remove");
}
show_pfh("remove", pfh);
return 0;
}
$ ./pid
open: fh = 3, name = /tmp/foo.pid
write: fh = 3, name = /tmp/foo.pid
close: fh = 0, name =
pid: pidfile_remove: Invalid argument
$ grep -iE 'name|version' /etc/os-release
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
PRETTY_NAME="Ubuntu 16.04 LTS"
VERSION_ID="16.04"
UBUNTU_CODENAME=xenial
$ gcc --version | grep ^gcc
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
$ ldd pid
linux-vdso.so.1 => (0x7fffc79b6000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7f72ee343000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f72edf79000)
/lib64/ld-linux-x86-64.so.2 (0x7f72ee558000)
** Affects: libbsd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1836219
Title:
pidfile_close prevents pidfile_remove from working
Status in libbsd package in Ubuntu:
New
Bug description:
The whole pidfile_xxx suite, besides being unnecessarily complicated
compared to 1 function in NetBSD, does not do what it says on the tin.
Complications. 4 functions instead of one. pidfile_open requires
pidptr, but doesn't use it. The other functions require an argument
that the documentation says isn't needed, but is.
Error. Most important, pidfile_close modifies its argument such that
pidfile_remove can't use it: both the file descriptor and the name are
destroyed.
The following program and associated output illustrates the problem.
#include
#include
#include
#include
void
show_pfh( const char func[], struct pidfh * pfh ) {
printf( "%s: fh = %d, name = %s\n", func, pfh->pf_fd, pfh->pf_path );
}
int
main(int argc, char *argv[])
{
pid_t pid;
struct pidfh * pfh = pidfile_open("/tmp/foo.pid", 0644, );
if( !pfh ) {
err(EXIT_FAILURE, "pidfile_open");
}
show_pfh("open", pfh);
if( -1 == pidfile_write(pfh) ) {
err(EXIT_FAILURE, "pidfile_write");
}
show_pfh("write", pfh);
if( -1 == pidfile_close(pfh) ) {
err(EXIT_FAILURE, "pidfile_close");
}
show_pfh("close", pfh);
if( -1 == pidfile_remove(pfh) ) {
err(EXIT_FAILURE, "pidfile_remove");
}
show_pfh("remove", pfh);
return 0;
}
$ ./pid
open: fh = 3, name = /tmp/foo.pid
write: fh = 3, name = /tmp/foo.pid
close: fh = 0, name =
pid: pidfile_remove: Invalid argument
$ grep -iE 'name|version' /etc/os-release
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
PRETTY_NAME="Ubuntu 16.04 LTS"
VERSION_ID="16.04"
UBUNTU_CODENAME=xenial
$ gcc --version | grep ^gcc
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
$ ldd pid
linux-vdso.so.1 => (0x7fffc79b6000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7f72ee343000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f72edf79000)
/lib64/ld-linux-x86-64.so.2 (0x7f72ee558000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1836219/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Re: motd [on at least some instances] does not auto-update daily
Hello Christian, or anyone else affected, Accepted base-files into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/10.1ubuntu2.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: base-files (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently
Dear William and Brian, Please test the updated Qt packages in -proposed and let us know your results and the version you tested with. Without this the update will not be released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Disco: Fix Committed Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Re: motd [on at least some instances] does not auto-update daily
Hello Christian, or anyone else affected, Accepted base-files into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/10.1ubuntu9.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: base-files (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: base-files (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: In Progress Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Please test proposed package
Hello Christian, or anyone else affected, Accepted base-files into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/base- files/10.1ubuntu7.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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: In Progress Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818812] Re: glib: Fix named destinations
I can't do it myself, I'll have to ask upstream to do it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704210] Re: NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1704210 Title: NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore Status in network-manager package in Ubuntu: Confirmed Bug description: As per the title; it looks (at first glance anyway, running TestNetworkManager.test_eth_dhcp6_off integration test from nplan) like NM does not set accept_ra to false, or provide a method for specifying whether you want to accept IPv6 RAs on that device. When IPv6 is disabled, we might also not want the kernel to heed RAs and create SLAAC addresses. NM already is able to disable accept_ra, since it does so when a device transitions to UNAVAILABLE or DISCONNECTED in some cases (see src/devices/nm-device.c). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
The Disco upload is in disco-unapproved waiting for the SRU Teams review now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836209] [NEW] network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Small clarification, I think the new Eoan merge with upstream will take care of the fix in comment #7. Nevertheless, the SRU for disco can be done with: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+ref/lp1831775 -disco-sru-iproute2 I need sponsoring for that ^. Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830867] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1830867 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830867] Re: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://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 1817537] Re: libsoup should support ntlmv2
Sorry to say that unfortunately it's not working here. Authentication through ntlm still not working: - installed package from proposed: --- libsoup2.4 (2.62.1-1ubuntu0.2) bionic; urgency=medium * debian/patches/git_ntlmv2_support.patch, debian/patches/git_ntlmv2_test.patch: - include upstream changes for NTLMv2 responses support, that's required for evolution-ews to be able to connect some exchange servers, also include corresponding code tests (lp: #1817537) -- Sebastien Bacher Tue, 09 Jul 2019 17:00:43 +0200 --- - rebooted - same problem: using ntlm in Evolution still not possible, authentication not working. Thanks for your work! -- 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/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Autopkgtest regression report (gtk+3.0/3.22.30-1ubuntu4)
All autopkgtests for the newly accepted gtk+3.0 (3.22.30-1ubuntu4) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Won't Fix Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date:
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
In the directory there are 10666 files, total size 735,5 MB. There are 723 .dds files with a total size of 248.2 MB >Could you run `tracker extract *` inside the problematic directory and see what happens There are various sub-directories with .dds files, running tracker inside them gives very similar outputs. Two outputs here https://pastebin.com/NTzha2Ww and here https://pastebin.com/MEiTzZPq It however doesn't loop forever, it just gives one error message for every single dds file and then exists properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
Hi, could you confirm that this bug is regarding all 3 gen Ryzen processors? I mean that 3400G (with integrated GPU) processor has Zen+ architecture but others have Zen2. Thanks. -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832123] Autopkgtest regression report (gst-plugins-good1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gst-plugins-good1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay:
[Touch-packages] [Bug 1832123] Autopkgtest regression report (gstreamer1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gstreamer1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep
[Touch-packages] [Bug 1832123] Autopkgtest regression report (gst-plugins-base1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gst-plugins-base1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay:
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer-vaapi into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gstreamer- vaapi/1.14.5-0ubuntu1~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gstreamer1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-ugly1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-ugly1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-python1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-python1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- python1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError -
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer-editing-services1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gstreamer-editing-services1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer-vaapi (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-base1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-base1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-good1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-good1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-good1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-rtsp-server1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst-rtsp- server1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a
[Touch-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-bad1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-bad1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-base1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Hello Amr, or anyone else affected, Accepted gst-libav1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- libav1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-libav1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists -
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
Hello Steve, or anyone else affected, Accepted gtk+3.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu4 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. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Won't Fix Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b
Re: [Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
On Thursday 11 July 2019 10:22:53 Markus Reuther wrote: > I am also affected by this issue: I would like to use my Jabra ENVOLVE > 65 headset with A2DP for the headphones in combination with the > microphone of the headset at the same time. Does your headset supports such feature? Ideally it is presented by vendor that this feature is supported? If yes, can you please describe how you are enabling this feature on headset? So we can look how to process it in pulseaudio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
I am also affected by this issue: I would like to use my Jabra ENVOLVE 65 headset with A2DP for the headphones in combination with the microphone of the headset at the same time. Hope that A2DP (for the headphones) and HSP/HFP (for the microphone) can be used simultaneously via Bluetooth and that someone finds out how and that someone fixes this. While this is not fixed I can not use my headset for voip calls under Ubuntu (18.04) (HSP/HFP quality is too poor for a multiple-hour call). -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio
*** This bug is a duplicate of bug 508522 *** https://bugs.launchpad.net/bugs/508522 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1828393 Title: Unable to use bluetooth headset with mic and a2dp audio Status in pulseaudio package in Ubuntu: Confirmed Bug description: Every device supports high fidelity audio while using headset with mic. This needs to enable two profiles at once: headset_head_unit and a2dp_sink. Right now this is impossible and I need to switch between profiles when listening to music and joining a call. In any case, the sound quality of HSP/HFP used in the headset_head_unit profile is horrible to have a call. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 9 13:20:26 2019 InstallationDate: Installed on 2018-11-20 (169 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1828393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836168] Re: Xorg freeze
1. Does the mouse pointer also freeze? 2. Does the bug occur if you log into Gnome Shell instead? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1836168 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 16:21:54 2019 DistUpgraded: 2019-07-03 23:09:43,158 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8368] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8368] InstallationDate: Installed on 2017-12-02 (586 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 0bda:58eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc5xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=9c7988f6-034d-45d2-bc6f-72ad962f2b90 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2019-07-03 (7 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8368 dmi.board.vendor: HP dmi.board.version: 46.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd07/28/2017:svnHP:pnHPPavilionLaptop15-cc5xx:pvrType1ProductConfigId:rvnHP:rn8368:rvr46.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc5xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jul 11 13:53:22 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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
My issue is in Xenial, so, no luck in testing that. -- 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: Fix Committed Status in pulseaudio source package in Cosmic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] 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 1818812] Re: glib: Fix named destinations
The issue was fixed in 0.73 which is in Disco
** Changed in: poppler (Ubuntu)
Importance: Undecided => Low
** Changed in: poppler (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818812] Re: glib: Fix named destinations
Would be probably fine for a SRU but the patch doesn't apply cleanly to
the current bionic version, could you try to backport/rebase it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
** Changed in: bzip2 Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2: Fix Released Status in bzip2 package in Ubuntu: In Progress Status in bzip2 source package in Xenial: Fix Released Status in bzip2 source package in Bionic: Fix Released Status in bzip2 source package in Cosmic: Fix Released Status in bzip2 source package in Disco: Fix Released Status in bzip2 package in Debian: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
I've sponsored the uploaded to Bionic now ** Changed in: gtk+3.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Won't Fix Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1836168] [NEW] Xorg freeze
Public bug reported: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 16:21:54 2019 DistUpgraded: 2019-07-03 23:09:43,158 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8368] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8368] InstallationDate: Installed on 2017-12-02 (586 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 0bda:58eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc5xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=9c7988f6-034d-45d2-bc6f-72ad962f2b90 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2019-07-03 (7 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8368 dmi.board.vendor: HP dmi.board.version: 46.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd07/28/2017:svnHP:pnHPPavilionLaptop15-cc5xx:pvrType1ProductConfigId:rvnHP:rn8368:rvr46.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc5xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jul 11 13:53:22 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1836168 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
[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
I've been using 1:11.1-1ubuntu7.3 for a couple of weeks already and have had no problems. But I would rather someone actually affected by this crash responds to comment #36. -- 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: Fix Committed Status in pulseaudio source package in Cosmic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] 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.
I've been using 1:11.1-1ubuntu7.3 for a couple of weeks already and have had no problems. But I would rather someone actually affected by this crash responds to comment #26. -- 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: Fix Committed Status in pulseaudio source package in Cosmic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Other Info] SRU sponsorship tracked in bug 1556439. [Original Report] 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
