[Touch-packages] [Bug 1780843] Re: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other in
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1780843 Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: New Bug description: The message in terminal (hungarian): Az alábbi csomagoknak teljesítetlen függőségei vannak depency problem ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-6 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 Date: Mon Jul 9 20:57:56 2018 DuplicateSignature: package:libperl5.26:5.26.2-6 Unpacking libperl5.26:i386 (5.26.2-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-RAPyb4/04-libperl5.26_5.26.2-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-03-30 (100 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha1 SourcePackage: perl Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1780843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] [NEW] After update 2018-07-08 menus and buttons are behaving badly
You have been subscribed to a public bug: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) ** Affects: libdrm (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- After update 2018-07-08 menus and buttons are behaving badly https://bugs.launchpad.net/bugs/1780846 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
I dont know enough to be sure whether or not libdrm-nouveau2 is the responsible package. But I will change the package on this ticket to that, if it helps get it more attention. ** Package changed: ubuntu => libdrm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in libdrm package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
** Description changed:
+ [Impact]
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
- AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
+ AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
+
+ [Test case]
+ cat > rootdir/etc/apt/apt.conf.d/99-json-hooks << EOF
+AptCli::Hooks::Install:: "true";
+AptCli::Hooks::Search:: "true";
+ EOF
+ and run an install.
+
+ This test and some more error handling tests are part of the test suite,
+ too, so autopkgtest covers that for us.
+
+ [Regression potential]
+ Hooks that do not respond to the initial handshake and just exit with 0 are
silently ignored.
+
+ [Other info]
+ There are some more changes in the patch that fix other cases of error
handling: As can be seen above, there are 2 error messages for one error,
because the code did not abort early, but tried to carry on, reading more data.
It now goes directly to the end.
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Bionic:
New
Bug description:
[Impact]
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
[Test case]
cat > rootdir/etc/apt/apt.conf.d/99-json-hooks << EOF
AptCli::Hooks::Install:: "true";
AptCli::Hooks::Search:: "true";
EOF
and run an install.
This test and some more error handling tests are part of the test
suite, too, so autopkgtest covers that for us.
[Regression potential]
Hooks that do not respond to the initial handshake and just exit with 0 are
silently ignored.
[Other info]
There are some more changes in the patch that fix other cases of error
handling: As can be seen above, there are 2 error messages for one error,
because the code did not abort early, but tried to carry on, reading more data.
It now goes directly to the end.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780099] Re: Cache remapping breaks hashing of Package objects
** Changed in: python-apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: python-apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1780099
Title:
Cache remapping breaks hashing of Package objects
Status in python-apt package in Ubuntu:
Fix Committed
Status in python-apt source package in Bionic:
In Progress
Bug description:
[Impact]
The apt.Package objects use the id as the hash, but the hash can change after
reopening, meaning that code will fail to work, for example:
c=apt.Cache()
p=c["a"]
set_of_p={p}
c.open()
assert p in set_of_p
will fail.
[Test case]
The above test case is run as part of autopkgtest (syntax is slightly
different), so passing autopkgtests means verification is done.
[Regression potential]
Hashing packages objects will be slower as it hashes the name and
architecture now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1780099/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
1.6.3 is in unapproved queue for bionic
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Bionic:
In Progress
Bug description:
[Impact]
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
[Test case]
cat > rootdir/etc/apt/apt.conf.d/99-json-hooks << EOF
AptCli::Hooks::Install:: "true";
AptCli::Hooks::Search:: "true";
EOF
and run an install.
This test and some more error handling tests are part of the test
suite, too, so autopkgtest covers that for us.
[Regression potential]
Hooks that do not respond to the initial handshake and just exit with 0 are
silently ignored.
[Other info]
There are some more changes in the patch that fix other cases of error
handling: As can be seen above, there are 2 error messages for one error,
because the code did not abort early, but tried to carry on, reading more data.
It now goes directly to the end.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie
** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: - The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. + [ Impact ] + * The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of apport binary package). + We should move the unit to apport package itself. - There is 2 possible solutions: + [ Test Case ] + * Install the new apport package from proposed + * Set in g-c-c, privacy panel, to report bugs automatically + * Make one program dumping a core dump + * Wait for a while, you should have a .upload and .uploaded files in addition to the .crash one in /var/crash + + [ Regression potential ] + The systemd units were in apport-noui previously, we moved them and made them conditional to whoopsie being installed. + apport-noui is still useful by turning autoreport on, so people upgrading shouldn't have any impact or difference. + The units have been renamed to make sense and avoid package files overwrite. + + - + There are 2 possible solutions: - promoting apport-noui to main, and seeding it. - or considering there is no reason anymore to have a separate apport-noui pacakge (no more phone factor), and so move the systemd units to apport, having a conditional file on whoopsie installed (no more dependency) and autoreport enabled, shipping those units binary package shipping those units (renamed to apport-autoreport.*) directly. ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778694 Title: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Bug description: [ Impact ] * The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of apport binary package). We should move the unit to apport package itself. [ Test Case ] * Install the new apport package from proposed * Set in g-c-c, privacy panel, to report bugs automatically * Make one program dumping a core dump * Wait for a while, you should have a .upload and .uploaded files in addition to the .crash one in /var/crash [ Regression potential ] The systemd units were in apport-noui previously, we moved them and made them conditional to whoopsie being installed. apport-noui is still useful by turning autoreport on, so people upgrading shouldn't have any impact or difference. The units have been renamed to make sense and avoid package files overwrite. - There are 2 possible solutions: - promoting apport-noui to main, and seeding it. - or considering there is no reason anymore to have a separate apport-noui pacakge (no more phone factor), and so move the systemd units to apport, having a conditional file on whoopsie installed (no more dependency) and autoreport enabled, shipping those units binary package shipping those units (renamed to apport-autoreport.*) directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
** Description changed: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. - We introduce 5 enw strings to translate: + We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
This bug was fixed in the package apt - 1.7.0~alpha2
---
apt (1.7.0~alpha2) experimental; urgency=medium
* Handle JSON hooks that just close the file/exit and fix some other errors
(LP: #1776218)
* Use cheaper entropy source for randomizing items to fetch
-- Julian Andres Klode Mon, 09 Jul 2018 16:02:45
+0200
** Changed in: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
In Progress
Bug description:
[Impact]
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
[Test case]
cat > rootdir/etc/apt/apt.conf.d/99-json-hooks << EOF
AptCli::Hooks::Install:: "true";
AptCli::Hooks::Search:: "true";
EOF
and run an install.
This test and some more error handling tests are part of the test
suite, too, so autopkgtest covers that for us.
[Regression potential]
Hooks that do not respond to the initial handshake and just exit with 0 are
silently ignored.
[Other info]
There are some more changes in the patch that fix other cases of error
handling: As can be seen above, there are 2 error messages for one error,
because the code did not abort early, but tried to carry on, reading more data.
It now goes directly to the end.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Description changed: - == xenial / trusty == - [Impact] - Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. - - APT relies on the ID of the package (it's position in the cache) for - it's operation. So if a package has ID 0 in the old cache, and a - different package has ID 0 in the new cache, performing operations on - the old package would perform it on the new package. If the old - package's ID is out of bounds in the new cache, the behavior is - undefined - it's an out of bounds array access. - - [Test case] - The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. - - More test cases like this are in the autopkgtest. - - [Regression potential] - The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. - - == bionic+ === - [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 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/. ** No longer affects: python-apt (Ubuntu Xenial) ** No longer affects: python-apt (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in update-manager source package in Trusty: Confirmed Status in update-manager source package in Xenial: Confirmed Status in python-apt source package in Bionic: Fix Released Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports abou
[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
** Description changed: + [Impact] + Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. + + APT relies on the ID of the package (it's position in the cache) for + it's operation. So if a package has ID 0 in the old cache, and a + different package has ID 0 in the new cache, performing operations on + the old package would perform it on the new package. If the old + package's ID is out of bounds in the new cache, the behavior is + undefined - it's an out of bounds array access. + + [Test case] + The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. + + More test cases like this are in the autopkgtest. + + [Regression potential] + The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. + + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 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/. ** Description changed: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. - + [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 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/. ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: New Status in unattended-upgrades source package in Trusty: Won't Fix Status in py
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
** Also affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
Test case for xenial / trusty ** Attachment added: "testcase.py" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737441/+attachment/5161874/+files/testcase.py ** Changed in: python-apt (Ubuntu Xenial) Status: Triaged => In Progress ** Summary changed: - /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string + python-apt crashes if objects of one cache are passed to depcache belonging to another cache -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: python-apt crashes if objects of one cache are passed to depcache belonging to another cache Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: New Status in unattended-upgrades source package in Trusty: Won't Fix Status in python-apt source package in Xenial: In Progress Status in unattended-upgrades source package in Xenial: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 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/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
I was hit by this exact problem (update to Ubuntu 18.04), the host command would hang and adding timeout works around the issue. Please put the temporary fix in so others are not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in avahi package in Debian: New Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Steve, which page size did you select when printing from evince? Can you also attach the PDF file which fails to print from evince? -- 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 cups-filters package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New 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 dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
It seems that evince has supplied a wrong name for the paper size. See these two lines in the error_log: [...] D [03/Jul/2018:12:22:01 -0700] [Job 489] argv[5]="InputSlot=Auto number-up=1 MediaType=Plain PageSize=Custom.Letter.SM noCollate OutputMode=Normal ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:a6bdd000-69b3-313b-6cfc-def9b98a0769 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1530645721 time-at-processing=1530645721" [...] D [03/Jul/2018:12:22:01 -0700] [Job 489] Ghostscript command line: gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=cups -sMediaType=Plain -sOutputType=0 -dDuplex -r600x300 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=0 -dDEVICEHEIGHTPOINTS=0 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=17 -scupsPageSizeName=Custom -I/usr/share/cups/fonts -c -f -_ [...] The client has sent the job with a "PageSize=Custom.Letter.SM" attribute and it should have used "Letter.SM". In the second line you see that in the Ghostscript command line zero got inserted for the width and the height of the page, due to the broken page size name. This is a bug of the client. As it occurs with evince it is most probably the print dialog of GTK. Adding GTK task ... ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Changed in: cups-filters (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New 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 dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:b
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
Turned cups task into cups-filters as one could improve the filters by putting an error message into error_log if the page size name is not correct. -- 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 cups-filters package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New 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 dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780995] [NEW] video drivers not working
Public bug reported: the intel video drivers not work in Dell optiplex 755 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 10 11:14:48 2018 DistUpgraded: 2018-07-09 20:33:32,337 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2018-04-06 (94 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. OptiPlex 755 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 12/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AF175320 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd12/09/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1780995 Title: video drivers not working Status in xorg package in Ubuntu: New Bug description: the intel video drivers not work in Dell optiplex 755 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 10 11:14:48 2018 DistUpgraded: 2018-07-09 20:33:32,337 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2018-04-06 (94 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. OptiPlex 755 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 12/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AF175320 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd12/09/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.l
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
Missing in this bug: kubuntu-settings ubuntu-gnome-defaults/xenial ubuntu-mate-artwork/xenial these are tracked in bug 1750465. ** Also affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: New Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: New Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: Triaged Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: New Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: New Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: New Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: New Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: New Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: New Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: New Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers ei
[Touch-packages] [Bug 1780996] [NEW] Convert triggers to noawait
Public bug reported: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have all triggering packages depend on them (e.g. B Depends A), or they need to be moved to noawait. This bug is about moving triggers to be noawait, by changing "activate" to "activate-noawait" and/or "interest" to "interest-noawait". If it turns out the trigger should be "await", we should explictly use the "interest-await" and "activate-await" variants in cosmic too. [Test case] There is no test case. [Regression potential] Packages triggering other packages are now configured even without the package being triggered being fully configured (they will be in the triggers-pending state). In most cases, this is not a problem. However, packages should be usable when configured, so for example, a package installing a gsettings schema would need to depend on the appropriate gsettings stuff and keep triggering it via await, as it would crash otherwise despite being configured. ** Affects: appstream (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: clutter-imcontext (Ubuntu) Importance: Undecided Status: New ** Affects: dochelp (Ubuntu) Importance: Undecided Status: New ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Affects: fusiondirectory (Ubuntu) Importance: Undecided Status: New ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: goopg (Ubuntu) Importance: Undecided Status: New ** Affects: gosa (Ubuntu) Importance: Undecided Status: New ** Affects: guile-2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: libomxil-bellagio (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mate-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: octave (Ubuntu) Importance: Undecided Status: New ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Affects: pike7.8 (Ubuntu) Importance: Undecided Status: New ** Affects: pike8.0 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New ** Affects: reconf-inetd (Ubuntu) Importance: Undecided Status: New ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Affects: sphinx (Ubuntu) Importance: Undecided Status: New ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Affects: xpdf (Ubuntu) Importance: Undecided Status: New ** Affects: yorick (Ubuntu) Importance: Undecided Status: New ** Affects: appstream (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: clutter-imcontext (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: dochelp (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: dovecot (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: fusiondirectory (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: gdk-pixbuf (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: goopg (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: gosa (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: guile-2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: hicolor-icon-theme (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: libomxil-bellagio (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: mate-icon-theme (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: octave (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: packagekit (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: pike7.8 (Ubuntu
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Description changed: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. + + [Impact] + "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. + + Triggers do not specify a ordering dependency however, so apt can very + well have A in a state where it is not configurable, and installing B + then fails. This is a limitation of triggers: They are not exposed in + Packages files, so we don't see them. + + What this means is that packages with await triggers either need to have + all triggering packages depend on them (e.g. B Depends A), or they need + to be moved to noawait. + + This bug is about moving triggers to be noawait, by changing "activate" + to "activate-noawait" and/or "interest" to "interest-noawait". If it + turns out the trigger should be "await", we should explictly use the + "interest-await" and "activate-await" variants in cosmic too. + + [Test case] + There is no test case. + + [Regression potential] + Packages triggering other packages are now configured even without the package being triggered being fully configured (they will be in the triggers-pending state). + + In most cases, this is not a problem. However, packages should be usable + when configured, so for example, a package installing a gsettings schema + would need to depend on the appropriate gsettings stuff and keep + triggering it via await, as it would crash otherwise despite being + configured. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: New Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: New Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: Triaged Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: New Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: New Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: New Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: New Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: New Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic:
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: xpdf (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: xpdf (Ubuntu) Status: New => Fix Released ** Changed in: xpdf (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: New Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: New Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: New Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: New Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: New Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: New Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have all triggering packages
[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
While waiting for a fix to this issue, I decided to put a *hold* on
these packages so that they won't be upgraded.
To place a hold on these packages using apt:
sudo apt-mark hold \
libegl1-mesa \
libgbm1 \
libgl1-mesa-dri \
libgl1-mesa-glx \
libglapi-mesa \
libgles2-mesa \
libosmesa6 \
libosmesa6 \
libwayland-egl1-mesa \
libxatracker2 \
mesa-vdpau-drivers
To list the packages on hold:
apt-mark showhold
Later if/when a fix is available the hold can be removed with:
sudo apt-mark unhold \
libegl1-mesa \
libgbm1 \
libgl1-mesa-dri \
libgl1-mesa-glx \
libglapi-mesa \
libgles2-mesa \
libosmesa6 \
libosmesa6 \
libwayland-egl1-mesa \
libxatracker2 \
mesa-vdpau-drivers
--
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/1780664
Title:
Recent libgl-mesa graphics update prevents drop down list menu
appearing in apps like firefox three line/bar menu icon
Status in mesa package in Ubuntu:
Confirmed
Bug description:
PROBLEM
Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
drop down list menu appearing in apps like firefox three line/bar menu
icon.
After recently applying updates, left clicking on some application
menus and icons no longer displays a drop-down menu list.
For example in Firefox when I left-click on the **three line/bar**
icon in the upper right-hand corner, the normal drop down list menu
does not display. Also the menu drop down doesn't display in
keypassx. Further xchat-gnome doesn't even display a window.
Another anomaly is that my KDE bottom menu bar changed to a dark
theme.
BACKGROUND
I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
Graphics. I have KDE **System Settings -> Compositor** enabled with:
Scale method :Accurate
Rendering backend: OpenGL 3.1
OpenGL interface: GLX
Tearing prevention ("vsync"): Full screen repaints
Keep window thumbnails:Only for Shown Windows
INVESTIGATION
After several hours of searching the Internet I found one other case
of a similar problem.
Firefox's Menu Bar won't open
https://support.mozilla.org/en-US/questions/1194760
The reported solution was to rollback the graphics drivers.
Because the issues cropped up after applying updates on July 6, 2018,
I tracked down the list of recent updates with:
grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
-1 >packages.txt
After some editing to place packages on separate lines, and
identifying the grahics libraries, I arrived at the following list:
--
libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
--
To revert to the prior graphic drivers I tracked down the '.deb'
packages for each of the above packages and downloaded the
'17.2.8-0ubuntu0~16.04.1' version.
For example:
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1
I also discovered that some of these depended on
libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:
libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb
WORKAROUND (ROLLBACK TO PRIOR VERSION)
Install older versions with:
sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: appstream (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: appstream (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: glib2.0 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: hicolor-icon-theme (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Fix Released ** Changed in: hicolor-icon-theme (Ubuntu Bionic) Status: New => Fix Released ** Changed in: hicolor-icon-theme (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: New Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: New Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: New Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Ne
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
Here's the commit for the change in Debian: https://salsa.debian.org/debian/xpdf/commit/7ef32acbb222f0f3433431a7329932056f667694 ** Changed in: xpdf (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: xpdf (Ubuntu Xenial) Status: New => In Progress ** Changed in: xpdf (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: xpdf (Ubuntu) Assignee: Brian Murray (brian-murray) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, s
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: mate-icon-theme (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: mate-icon-theme (Ubuntu) Status: New => Fix Released ** Changed in: mate-icon-theme (Ubuntu Bionic) Status: New => Fix Released ** Changed in: mate-icon-theme (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: New Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: New Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limit
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
Sphinx in cosmic no longer uses triggers. Sphinx in bionic uses interest-noawait. ** Changed in: sphinx (Ubuntu) Status: New => Fix Released ** Changed in: sphinx (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: New Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: sphinx (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: sphinx (Ubuntu Xenial) Status: New => In Progress ** Changed in: sphinx (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: New Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: New Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't
[Touch-packages] [Bug 1781022] [NEW] Video's frame stuck, but audio is still running
Public bug reported: This problem happened when I'm playing a MP4 video. It suddenly stucks at some frames for 3-5 seconds, then it will continue to a corresponding frame. During the frame stuck, the audio is still running. Especially, if I move mouse cursor right after the stucking frame, it will continue play immediately. And it means if I keep moving the cursor, the video will never stuck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 Uname: Linux 4.17.0-041700-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 00:26:46 2018 InstallationDate: Installed on 2018-05-07 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - This problem happened when I'm playing a MP4 video. It suddenly stucks at some frame for 3-5 seconds, then it will continue to a corresponding frame. During the frame stuck, the audio is still running. + This problem happened when I'm playing a MP4 video. It suddenly stucks at some frames for 3-5 seconds, then it will continue to a corresponding frame. During the frame stuck, the audio is still running. Especially, if I move mouse cursor right after the stucking frame, it will continue play immediately. And it means if I keep moving the cursor, the video will never stuck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 Uname: Linux 4.17.0-041700-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 00:26:46 2018 InstallationDate: Installed on 2018-05-07 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1781022 Title: Video's frame stuck, but audio is still running Status in gstreamer1.0 package in Ubuntu: New Bug description: This problem happened when I'm playing a MP4 video. It suddenly stucks at some frames for 3-5 seconds, then it will continue to a corresponding frame. During the frame stuck, the audio is still running. Especially, if I move mouse cursor right after the stucking frame, it will continue play immediately. And it means if I keep moving the cursor, the video will never stuck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 Uname: Linux 4.17.0-041700-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 00:26:46 2018 InstallationDate: Installed on 2018-05-07 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1781022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: clutter-1.0 (Ubuntu) Status: New => Confirmed -- 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/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GStreamer: Confirmed Status in GTK+: Fix Released Status in totem-pl-parser: Expired Status in clutter-1.0 package in Ubuntu: Confirmed Status in clutter-gst-3.0 package in Ubuntu: Incomplete Status in clutter-gtk package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Fix Released Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1698270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: tex-common (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tex-common (Ubuntu) Status: New => Fix Released ** Changed in: tex-common (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: New Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Pac
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: tex-common (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: New Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have all triggering packages depend on them (e.g. B Depend
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
Here's the yorick upstream change: https://salsa.debian.org/science- team/yorick/commit/2266af43e759aee5c5f4afdf085c1bb23105412a The important bit was just the trigger file. ** Changed in: yorick (Ubuntu Xenial) Status: New => In Progress ** Changed in: yorick (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: New Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: New Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: New Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: New Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is
[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
@diepes, interesting. Looks like there was a loop going on there.
Can everybody please check their /etc/resolv.conf to see if something
similar might be happening with it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M77 Ver. 01.05
dmi.board.name: 2271
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.4C
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: yorick (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: New Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have al
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: gdk-pixbuf (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Fix Released ** Changed in: gdk-pixbuf (Ubuntu Bionic) Status: New => Fix Released ** Changed in: gdk-pixbuf (Ubuntu Xenial) Status: New => In Progress ** Changed in: shared-mime-info (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: shared-mime-info (Ubuntu) Status: New => Fix Released ** Changed in: shared-mime-info (Ubuntu Bionic) Status: New => Fix Released ** Changed in: shared-mime-info (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in goopg package in Ubuntu: New Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: New Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in goopg source package in Xenial: New Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: New Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in goopg source package in Bionic: New Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: New Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: Thi
Re: [Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I hope that is good news! How do I install the fix on my system - the link seems to be to source code? I am very busy at the moment, and may not be able to do much testing till next week. On 10/07/18 02:42, Daniel van Vugt wrote: > Yes that was released a few hours ago: > https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20 > > George: as the original reporter can you confirm that today's update to > the 'linux-firmware' package has fixed it? > > ** Changed in: linux-firmware (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: bluez (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: bluez (Ubuntu) > Status: Incomplete => Invalid > > ** Changed in: linux (Ubuntu) > Status: Incomplete => Invalid > -- George Hunter 10A Roome Bay Crescent CrailTel 01333 451 442 Fife KY10 3TTEmail ad...@roomebay.me.uk UK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Incomplete Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci0 24:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCO
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
Turns out goopg was not affected, it does not exist in xenial. ** No longer affects: goopg (Ubuntu) ** No longer affects: goopg (Ubuntu Bionic) ** No longer affects: goopg (Ubuntu Xenial) ** Changed in: packagekit (Ubuntu) Status: New => Fix Released ** Changed in: packagekit (Ubuntu Bionic) Status: New => Fix Released ** Changed in: packagekit (Ubuntu Xenial) Status: New => In Progress ** Changed in: appstream (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: appstream (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) ** Changed in: gdk-pixbuf (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: gdk-pixbuf (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) ** Changed in: glib2.0 (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) ** Changed in: glib2.0 (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: hicolor-icon-theme (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: hicolor-icon-theme (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) ** Changed in: mate-icon-theme (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: mate-icon-theme (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) ** Changed in: packagekit (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: shared-mime-info (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: shared-mime-info (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source pa
[Touch-packages] [Bug 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1
Verified with unattended-upgrades 1.1ubuntu1.18.04.1. Log: root@bb-uu-fixed:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.1 all automatic installation of security upgrades root@bb-uu-fixed:~# apt update && unattended-upgrade --dry-run --verbose Hit:1 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Option --dry-run given, *not* performing real actions Packages that will be upgraded: libgcrypt20 libssl1.0.0 libssl1.1 openssl Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libgcrypt20_1.8.1-4ubuntu1.1_amd64.deb /usr/bin/dpkg --status-fd 9 --no-triggers --configure libgcrypt20:amd64 /usr/bin/dpkg --status-fd 9 --configure --pending Preconfiguring packages ... /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libssl1.0.0_1.0.2n-1ubuntu5.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending Preconfiguring packages ... /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libssl1.1_1.1.0g-2ubuntu4.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/openssl_1.1.0g-2ubuntu4.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending All upgrades installed root@bb-uu-fixed:~# apt update && unattended-upgrade --dry-run --verbose --debug Hit:1 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic adjusting candidate version: apache2=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-bin=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-data=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-dbg=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-dev=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-doc=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-ssl-dev=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-suexec-custom=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-suexec-pristine=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-utils=2.4.29-1ubuntu4.1 adjusting candidate version: apport-gtk=2.20.9-0ubuntu7.1 adjusting candidate version: apport-kde=2.20.9-0ubuntu7.1 adjusting candidate version: apport-noui=2.20.9-0ubuntu7.1 adjusting candidate version: apport-retrace=2.20.9-0ubuntu7.1 adjusting candidate version: apport-valgrind=2.20.9-0ubuntu7.1 adjusting candidate version: apt=1.6.1 adjusting candidate version: apt-doc=1.6.1 adjusting candidate version: apt-transport-https=1.6.1 adjusting candidate version: apt-utils=1.6.1 adjusting candidate version: bluedevil=4:5.12.4-0ubuntu1 adjusting candidate version: boinc=7.9.3+dfsg-5 adjusting candidate version: boinc-client=7.9.3+dfsg-5 adjusting candidate version: boinc-client-nvidia-cuda=7.9.3+dfsg-5 adjusting candidate version: boinc-client-opencl=7.9.3+dfsg-5 adjusting candidate version: boinc-dev=7.9.3+dfsg-5 adjusting candidate version: boinc-manager=7.9.3+dfsg-5 adjusting candidate version: boinc-screensaver=7.9.3+dfsg-5 adjusting candidate version: boinc-virtualbox=7.9.3+dfsg-5 adjusting candidate version: bolt=0.2-0ubuntu1 adjusting candidate version: breeze=4:5.12.4-0ubuntu1 adjusting candidate version: breeze-cursor-theme=4:5.12.4-0ubuntu1 adjusting candidate version: breeze-d
[Touch-packages] [Bug 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version
Verified with unattended-upgrades 1.1ubuntu1.18.04.1. Log: root@bb-uu-fixed:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.1 all automatic installation of security upgrades root@bb-uu-fixed:~# apt update && unattended-upgrade --dry-run --verbose Hit:1 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Option --dry-run given, *not* performing real actions Packages that will be upgraded: libgcrypt20 libssl1.0.0 libssl1.1 openssl Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libgcrypt20_1.8.1-4ubuntu1.1_amd64.deb /usr/bin/dpkg --status-fd 9 --no-triggers --configure libgcrypt20:amd64 /usr/bin/dpkg --status-fd 9 --configure --pending Preconfiguring packages ... /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libssl1.0.0_1.0.2n-1ubuntu5.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending Preconfiguring packages ... /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/libssl1.1_1.1.0g-2ubuntu4.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/openssl_1.1.0g-2ubuntu4.1_amd64.deb /usr/bin/dpkg --status-fd 9 --configure --pending All upgrades installed root@bb-uu-fixed:~# apt update && unattended-upgrade --dry-run --verbose --debug Hit:1 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic adjusting candidate version: apache2=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-bin=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-data=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-dbg=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-dev=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-doc=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-ssl-dev=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-suexec-custom=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-suexec-pristine=2.4.29-1ubuntu4.1 adjusting candidate version: apache2-utils=2.4.29-1ubuntu4.1 adjusting candidate version: apport-gtk=2.20.9-0ubuntu7.1 adjusting candidate version: apport-kde=2.20.9-0ubuntu7.1 adjusting candidate version: apport-noui=2.20.9-0ubuntu7.1 adjusting candidate version: apport-retrace=2.20.9-0ubuntu7.1 adjusting candidate version: apport-valgrind=2.20.9-0ubuntu7.1 adjusting candidate version: apt=1.6.1 adjusting candidate version: apt-doc=1.6.1 adjusting candidate version: apt-transport-https=1.6.1 adjusting candidate version: apt-utils=1.6.1 adjusting candidate version: bluedevil=4:5.12.4-0ubuntu1 adjusting candidate version: boinc=7.9.3+dfsg-5 adjusting candidate version: boinc-client=7.9.3+dfsg-5 adjusting candidate version: boinc-client-nvidia-cuda=7.9.3+dfsg-5 adjusting candidate version: boinc-client-opencl=7.9.3+dfsg-5 adjusting candidate version: boinc-dev=7.9.3+dfsg-5 adjusting candidate version: boinc-manager=7.9.3+dfsg-5 adjusting candidate version: boinc-screensaver=7.9.3+dfsg-5 adjusting candidate version: boinc-virtualbox=7.9.3+dfsg-5 adjusting candidate version: bolt=0.2-0ubuntu1 adjusting candidate version: breeze=4:5.12.4-0ubuntu1 adjusting candidate version: breeze-cursor-theme=4:5.12.4-0ubuntu1 adjusting candidate version: breeze-dev=4:5.12.4-0ubuntu1 adjusting candidate version: budgie-desktop-common=0.9.9 adjusti
[Touch-packages] [Bug 1781049] [NEW] WiFI hard blocked after resuming laptop (RTL 8723BE)
Public bug reported: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bionic rtl8723be wifi -- 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/1781049 Title: WiFI hard blocked after resuming laptop (RTL 8723BE) Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Verified with 1.1ubuntu1.18.04.1:
Log from shell "A":
rbalint@xenial-test:~$ lxc exec bb-uu-fixed -- bash
root@bb-uu-fixed:~# unattended-upgrade --dry-run --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: libgcrypt20 libssl1.0.0 libssl1.1 openssl
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/libgcrypt20_1.8.1-4ubuntu1.1_amd64.deb
/usr/bin/dpkg --status-fd 9 --no-triggers --configure libgcrypt20:amd64
/usr/bin/dpkg --status-fd 9 --configure --pending
Preconfiguring packages ...
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/libssl1.0.0_1.0.2n-1ubuntu5.1_amd64.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
Preconfiguring packages ...
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/libssl1.1_1.1.0g-2ubuntu4.1_amd64.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/openssl_1.1.0g-2ubuntu4.1_amd64.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
All upgrades installed
Attaching log for shell "B", since it is quite long.
In the attached log it can be observed that the lock is still lost by u-u for
small windows (due to python-apt losing it), but u-u then reacquires it, which
is what the fix for u-u should do.
Unfixed unattended-upgrades 1.1ubuntu1, shell "B":
root@bb-uu:~# while sleep 0.3; do python3 -c 'import apt; import apt_pkg;
print(apt_pkg.pkgsystem_lock())' ; done
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
True
^C
root@bb-uu:~# exit
In the unfixed version u-u just loses the lock.
** Attachment added: "u-u-1.1ubuntu1.18.04.1-shell-B.log"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1602536/+attachment/5162110/+files/u-u-1.1ubuntu1.18.04.1-shell-B.log
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536
Title:
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
/unattended-
upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Status in python-apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
New
Status in python-apt source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Unattended-upgrades fails to autoremove packages after installing
updates or fails to install updates due to a parallel process
acquiring apt or dpkg lock while u-u is running.
[Test Case]
* Set up a system with packages (> 30) to be upgraded. In case of
Bionic -security has a low number of updates, thus set up the system
to install -updates to have more packages for u-u to upgrade:
echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51-updates
* Set
[Touch-packages] [Bug 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.1 --- unattended-upgrades (1.1ubuntu1.18.04.1) bionic; urgency=medium [ Michael Vogt ] * unattended-upgrades: fix Unlocked context manager. (LP: #1602536) The Unlocked context manager did correctly unlock but did not reacquire the lock which means that in minimal-upgrade step mode it is possible to run apt code without a lock. If something else (like landscape, apt, synaptic, packagekit) locks the cache in the meantime this will work and u-u will get dpkg errors because dpkg will not be able to perform its operations. It is less of an issue in non-minimal mode, but even then the auto-remove step may fail in this way. [ Balint Reczey ] * Fix adjusting candidates (LP: #1775292) * Relock apt lock before reopening the cache (LP: #1602536) * Fix crashing while adjusting candidates and save candidates to adjust only in first sweep run, not emptying the set later (Closes: #901258) (LP: #1775307) -- Balint Reczey Wed, 06 Jun 2018 16:30:55 -0700 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1775307 Title: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades fails to install updates when adjusting candidates is needed. [Test Case] Note that only 1.2ubuntu1 is affected. Earlier releases either did not crash or did not adjust candidates due to LP: #1775292. To reproduce the crash Cosmic's u-u 1.2ubuntu1 needs to be installed. * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " or a crash with buggy u-u versions ... adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15 adjusting candidate version: zfs-test=0.7.5-1ubuntu15 adjusting candidate version: zfs-zed=0.7.5-1ubuntu15 adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1928, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1554, in main allowed_origins=allowed_origins) File "/usr/bin/unattended-upgrade", line 122, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 152, in open self.adjust_candidates() File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates for pkgname, candidate in self._get_candidates_to_adjust(): ValueError: too many values to unpack (expected 2) * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " and no crash [Regression Potential] * Unattended-upgrade may crash when adjusting candidates preventing upgrades to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775307] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1775307 Title: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades fails to install updates when adjusting candidates is needed. [Test Case] Note that only 1.2ubuntu1 is affected. Earlier releases either did not crash or did not adjust candidates due to LP: #1775292. To reproduce the crash Cosmic's u-u 1.2ubuntu1 needs to be installed. * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " or a crash with buggy u-u versions ... adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15 adjusting candidate version: zfs-test=0.7.5-1ubuntu15 adjusting candidate version: zfs-zed=0.7.5-1ubuntu15 adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1928, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1554, in main allowed_origins=allowed_origins) File "/usr/bin/unattended-upgrade", line 122, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 152, in open self.adjust_candidates() File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates for pkgname, candidate in self._get_candidates_to_adjust(): ValueError: too many values to unpack (expected 2) * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " and no crash [Regression Potential] * Unattended-upgrade may crash when adjusting candidates preventing upgrades to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775292] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1775292 Title: Unattended-upgrades stopped adjusting candidates in 1.1 Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades may fail to install an update when the highest version of a package to be updated exists in an origin u-u is not allowed to pull packages from. [Test Case] * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " with buggy u-u version * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " [Regression Potential] * Unattended-upgrade may crash when adjusting candidates preventing upgrades to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.1 --- unattended-upgrades (1.1ubuntu1.18.04.1) bionic; urgency=medium [ Michael Vogt ] * unattended-upgrades: fix Unlocked context manager. (LP: #1602536) The Unlocked context manager did correctly unlock but did not reacquire the lock which means that in minimal-upgrade step mode it is possible to run apt code without a lock. If something else (like landscape, apt, synaptic, packagekit) locks the cache in the meantime this will work and u-u will get dpkg errors because dpkg will not be able to perform its operations. It is less of an issue in non-minimal mode, but even then the auto-remove step may fail in this way. [ Balint Reczey ] * Fix adjusting candidates (LP: #1775292) * Relock apt lock before reopening the cache (LP: #1602536) * Fix crashing while adjusting candidates and save candidates to adjust only in first sweep run, not emptying the set later (Closes: #901258) (LP: #1775307) -- Balint Reczey Wed, 06 Jun 2018 16:30:55 -0700 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1775292 Title: Unattended-upgrades stopped adjusting candidates in 1.1 Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades may fail to install an update when the highest version of a package to be updated exists in an origin u-u is not allowed to pull packages from. [Test Case] * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " with buggy u-u version * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " [Regression Potential] * Unattended-upgrade may crash when adjusting candidates preventing upgrades to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
The bucket for the 18.04 version of this crash,
https://errors.ubuntu.com/problem/33db55f3a084a7957ca1ec76f7ac2870614f17fa,
only contains a few instances of the new package version and that's
likely due to apport gathering the package version number after the
crash occurs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536
Title:
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
/unattended-
upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Status in python-apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
New
Status in python-apt source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades fails to autoremove packages after installing
updates or fails to install updates due to a parallel process
acquiring apt or dpkg lock while u-u is running.
[Test Case]
* Set up a system with packages (> 30) to be upgraded. In case of
Bionic -security has a low number of updates, thus set up the system
to install -updates to have more packages for u-u to upgrade:
echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51-updates
* Set up two shells to run commands in parallel
* In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run
--verbose --debug
* After u-u started run the following command in shell "B":
while sleep 1; do python3 -c 'import apt; import apt_pkg;
print(apt_pkg.pkgsystem_lock())' ; done
* Observe the following exception repeated while running u-u and True being
printed after u-u is finished:
...
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
True
True
True
...
[Regression Potential WIP]
* Unattended-upgrade may crash
[Other Info]
It looks like python-apt also releases the lock sometimes unexpectedly
thus the both packages need to be fixed to avoid loosing the lock.
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen
with version 0.90, the problem page at
https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1602536/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
I'd like to revive this bug report. I have both an HP 9480m and a 9470m and two of these HP Slim docks and have this same issue with them as is reported here. I've attempted the workarounds that have been reported, but have yet to find any success. (I'm still methodically working through the channel group/channel-in-group settings in HDAJackRetask.) That said, looking back through google searches, it appears that this has been a problem since, roughly the dawn of time. I've got time and a vested interest in making this work, so if I could get some assistance in making this fly, I would appreciate it and then we can document it and submit a bug fix for the betterment of the community experience. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from "internal microphone" to "microphone" in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. Plugging in microphone to line in on docking station, nothing happens. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.1
---
unattended-upgrades (1.1ubuntu1.18.04.1) bionic; urgency=medium
[ Michael Vogt ]
* unattended-upgrades: fix Unlocked context manager. (LP: #1602536)
The Unlocked context manager did correctly unlock but did not
reacquire the lock which means that in minimal-upgrade step
mode it is possible to run apt code without a lock. If something
else (like landscape, apt, synaptic, packagekit) locks the cache
in the meantime this will work and u-u will get dpkg errors
because dpkg will not be able to perform its operations. It is
less of an issue in non-minimal mode, but even then the auto-remove
step may fail in this way.
[ Balint Reczey ]
* Fix adjusting candidates (LP: #1775292)
* Relock apt lock before reopening the cache (LP: #1602536)
* Fix crashing while adjusting candidates and save candidates to adjust only
in first sweep run, not emptying the set later
(Closes: #901258) (LP: #1775307)
-- Balint Reczey Wed, 06 Jun 2018 16:30:55 -0700
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536
Title:
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
/unattended-
upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Status in python-apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
New
Status in python-apt source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades fails to autoremove packages after installing
updates or fails to install updates due to a parallel process
acquiring apt or dpkg lock while u-u is running.
[Test Case]
* Set up a system with packages (> 30) to be upgraded. In case of
Bionic -security has a low number of updates, thus set up the system
to install -updates to have more packages for u-u to upgrade:
echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51-updates
* Set up two shells to run commands in parallel
* In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run
--verbose --debug
* After u-u started run the following command in shell "B":
while sleep 1; do python3 -c 'import apt; import apt_pkg;
print(apt_pkg.pkgsystem_lock())' ; done
* Observe the following exception repeated while running u-u and True being
printed after u-u is finished:
...
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
True
True
True
...
[Regression Potential WIP]
* Unattended-upgrade may crash
[Other Info]
It looks like python-apt also releases the lock sometimes unexpectedly
thus the both packages need to be fixed to avoid loosing the lock.
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen
with version 0.90, the problem page at
https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1602536/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602536] Update Released
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536
Title:
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
/unattended-
upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Status in python-apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
New
Status in python-apt source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades fails to autoremove packages after installing
updates or fails to install updates due to a parallel process
acquiring apt or dpkg lock while u-u is running.
[Test Case]
* Set up a system with packages (> 30) to be upgraded. In case of
Bionic -security has a low number of updates, thus set up the system
to install -updates to have more packages for u-u to upgrade:
echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51-updates
* Set up two shells to run commands in parallel
* In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run
--verbose --debug
* After u-u started run the following command in shell "B":
while sleep 1; do python3 -c 'import apt; import apt_pkg;
print(apt_pkg.pkgsystem_lock())' ; done
* Observe the following exception repeated while running u-u and True being
printed after u-u is finished:
...
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
True
True
True
...
[Regression Potential WIP]
* Unattended-upgrade may crash
[Other Info]
It looks like python-apt also releases the lock sometimes unexpectedly
thus the both packages need to be fixed to avoid loosing the lock.
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen
with version 0.90, the problem page at
https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1602536/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780707] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1780707 Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After installing a fresh install of ubuntu 18.04, the software updater asked me to update and after saying yes, it reported this error about initramfs-tools. Also, another error just appeared which is much worse ... Here is what the dialog says: An unhandlable error occured There seems to be a programming error in aptdaemon, the software that allows you to install/remove software and to perform other package management related tasks. Not that the install was a full erase of a partition and now an update or merge ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 8 22:33:38 2018 Df: Dmesg: ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-07-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1780707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
The following tests have a history of failures and shouldn't be considered regressions: dulwich [bionic/s390x] snapcraft [bionic/all arches] python-mechanicalsoup [bionic/all arches] These LinkNotFoundErrors also occurred in cosmic and when the bionic/s390x version was triggered by pytest-mock/1.7.1-1 so its not related to my SRU. netplan.io [bionic/all arches] test_eth_dhcp6_off seems flaky to me as its failed with other triggers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 I've experienced this bug in a clean install of 18.04 via the server edition first then adding a GUI. In the past editing /etc/NetworkManager/NetworkManager.conf and setting managed=true was the solution, that doesn't work anymore. Instead, first I needed to create a file under /usr/lib/NetworkManager/conf.d/10-globally-managed- devices.conf and put the following text in it: [keyfile] unmanaged-devices=*,except:type:wifi,except:type:wwan then copy that file to /etc/NetworkManager/conf.d/10-globally-managed- devices.conf and then edit the file /etc/NetworkManager/conf.d/10-globally-managed- devices.conf and change the line to say unmanaged-devices=none that is finally, at long last what solved it for me. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
The following tests have a history of failures and shouldn't be considered regressions: xandikos [artful/ppc64el] it regularly has autopkgtest timeouts for all arches and release meson [artful/i386] sometimes passes but sometimes fails always in simdtest network-manager [artful/arm64] almost never passes pyfai [artful/all arches] fails more often than it passes on most arches unattended-upgrades [bionic/arm64] has failed repeatedly python-docker [artful/s390x] client timeout errors on everything but armhf firewall? translate-toolkit [artful/all arches] seems unrelated given that it fails on all arches and nothing has triggered translate-toolkit in 8 or 9 months so infrastructure? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778140] Re: resize2fs hoses a filesystem on lvm after resizing
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1778140 Title: resize2fs hoses a filesystem on lvm after resizing Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Resized an ext4 filesystem on LVM. Before resizing, I confirmed filesystem was clean with e2fsck. After resizing, three errors were found. root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root e2fsck 1.44.1 (24-Mar-2018) Pass 1: Checking inodes, blocks, and sizes Inode 21110 extent block passes checks, but checksum does not match extent (logical block 18432, physical block 503808, len 3813) Fix? no Inode 26807 extent block passes checks, but checksum does not match extent (logical block 34816, physical block 768000, len 896) Fix? no Inode 28306 extent block passes checks, but checksum does not match extent (logical block 30720, physical block 430080, len 5130) Fix? no Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information This setup is currently in a virtual machine with a snapshot, so I can revert back and retest. The resize2fs is coming from the 18.04 Ubuntu CD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: e2fsprogs 1.44.1-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 21:03:56 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310192] Re: package cups 1.6.1-0ubuntu11.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello Anitshrestha Thank you for submitting this bug and reporting a problem with updating the cups package. You made this bug report in 2014 and there have been several versions of Ubuntu and cups since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you run the following (only once): apport-collect 1310192 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu and cups better. G ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1310192 Title: package cups 1.6.1-0ubuntu11.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: Incomplete Bug description: anit@anit-ThinkPad-T520:~$ sudo apt-get upgrade [sudo] password for anit: Sorry, try again. [sudo] password for anit: Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: apport apport-gtk cups-filters firefox gir1.2-gtk-3.0 gnome-online-accounts gnome-screensaver initramfs-tools initramfs-tools-bin language-selector-common language-selector-gnome libcupsfilters1 libgail-3-0 libgoa-1.0-0 libgoa-1.0-common libgtk-3-0 libgtk-3-bin libgtk-3-common libpoppler-glib8 libpython2.7 librsvg2-2 librsvg2-common libxml2 libxml2:i386 poppler-utils python-libxml2 python2.7 python2.7-minimal software-properties-common software-properties-gtk telepathy-gabble telepathy-idle thunderbird thunderbird-gnome-support thunderbird-locale-en udisks 0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Y Setting up cups (1.6.1-0ubuntu11.5) ... AppArmor parser error for /etc/apparmor.d/usr.sbin.cupsd in /etc/apparmor.d/usr.sbin.cupsd at line 24: Invalid capability block_suspend. start: Job failed to start invoke-rc.d: initscript cups, action "start" failed. dpkg: error processing cups (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of printer-driver-hpcups: printer-driver-hpcups depends on cups; however: Package cups is not configured yet. dpkg: error processing printer-driver-hpcups (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of hplip: hplip depends on printer-driver-hpcups (= 3.12.6-3ubuntu4.3); however: Package printer-driver-hpcups is not configured yet. hplip depends on cups (>= 1.1.20); however: Package cups is not configured yet. dpkg: error processing hplip (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Errors were encountered while processing: cups printer-driver-hpcups hplip E: Sub-process /usr/bin/dpkg returned an error code (1) anit@anit-ThinkPad-T520:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: apport apport-gtk cups-filters firefox gir1.2-gtk-3.0 gnome-online-accounts gnome-screensaver initramfs-tools initramfs-tools-bin language-selector-common language-selector-gnome libcupsfilters1 libgail-3-0 libgoa-1.0-0 libgoa-1.0-common libgtk-3-0 libgtk-3-bin libgtk-3-common libpoppler-glib8 libpython2.7 librsvg2-2 librsvg2-common libxml2 libxml2:i386 poppler-utils python-libxml2 python2.7 python2.7-minimal software-properties-common software-properties-gtk telepathy-gabble telepathy-idle thunderbird thunderbird-gnome-support thunderbird-locale-en udisks 0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Y Setting up cups (1.6.1-0ubuntu11.5) ... AppArmor parser error for /etc/apparmor.d/usr.sbin.cupsd in /etc/apparmor.d/usr.sbin.cupsd at line 24: Invalid capability block_suspend. start: Job failed to start invoke-rc.d: initscript cups, action "start" failed. dpkg: erro
[Touch-packages] [Bug 1325525] Re: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d
Hello Dexter, Thank you for submitting this bug and reporting a problem with the fontconfig package. You made this bug report in 2014 and there have been several versions of Ubuntu since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you run the following (only once): apport-collect 1325525 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: fontconfig (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1325525 Title: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d Status in fontconfig package in Ubuntu: Incomplete Bug description: I've just installed Ubuntu-trusty, and noticed that in Thunderbird the fonts are rendered incorrectly. It seemed that the problem is with sub-pixel rendering. After much googling and finding nothing I've started to compare the /etc/fonts/conf.d dir on my Precise machin with the trusty one. I noticed that on trusty the 53-monospace-lcd-filter.conf file is missing from the conf.d dir, but is available in the conf.avail. After I created the symlink and rebooted, my thunderbird font rendering became normal again. But now if I start from something from the terminal it says: "Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected" So the 1st question, why did you leave out the monospace-lcd- filter.conf from the fontconfig conf.d, and the second is why didn't you update it so it won't complaing about the multiple test tags. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 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: Mon Jun 2 12:43:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:308c] MachineType: LENOVO 3492C4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=a1bd4186-b465-4605-845f-12c9de2dc180 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: F1KT44AUS dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrF1KT44AUS:bd12/21/2012:svnLENOVO:pn3492C4G:pvrThinkCentreEdge72:rvnLENOVO:rn:rvrNODPK:cvnLENOVO:ct3:cvr: dmi.product.name: 3492C4G dmi.product.version: ThinkCentre Edge72 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 2 12:37:17 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16498 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launc
[Touch-packages] [Bug 1319705] Re: Cyrus IMAP shared folders do not work in Evolution
Hello bugreports2005, Thank you for submitting this bug and reporting a problem with imap shared folders in Evolution. You made this bug report in 2014 and there have been several versions of Ubuntu and Evolution since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you run the following (only once): apport-collect 1319705 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu and Evolution better. G ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1319705 Title: Cyrus IMAP shared folders do not work in Evolution Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 LTS evolution 3.10.4-0ubuntu1 evolution-data-server 3.10.4-0ubuntu1 I expected to be able to use shared folders on a Cyrus IMAP server, but instead I only get a message saying "There are no messages in this folder." Thunderbird has no problem working with the shared folders. This appears to be a problem of the "IMAP+" server type, which also affects earlier versions of Evolution (tried on 2.32.3). However, the older version also supports an "IMAP" server type that works as expected, but this is no longer available in newer versions of Evolution. This has been reported upstream and there appear to be patches: https://bugzilla.gnome.org/show_bug.cgi?id=678216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1319705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1335627] Re: Is asking for passwords to access already set ups of User Accounts with OpenGPL Pub key, the password has been saved to a KeyRing File . One a Password request pop u
Hello Xreuze, Thank you for submitting this bug and reporting a problem with the gcr package. You made this bug report in 2014 and there have been several versions of Ubuntu since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you run the following (only once): apport-collect 1335627 and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: gcr (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1335627 Title: Is asking for passwords to access already set ups of User Accounts with OpenGPL Pub key, the password has been saved to a KeyRing File . One a Password request pop up window comes up asking for re-enter passwords in a Keyring stops the keyboard, can not type anything unless clicking cancel or submit ok key so it will be re saved. When i open Thunderbird up, it asks it again . I had Gnome Evolution Mail which is using same dependcie files with Thunderbird. I used Synapsis to remove the Evolution etc. Every reboot this whole starts again. OpenGPL is on file for crypto to gmail and yahoo in Emphaty and Access given to Ubuntu server to keep track when opening clients. Status in gcr package in Ubuntu: Incomplete Bug description: I have looked on the keyring lib's but i can not see the bug be part of there. This is maybe a Mail Client or chat client dependency file problem need a wrapper that ends the loop. The bug does exist in the gcr file , i think there is a open argument that is with out a wrapper that ends the loop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcr 3.10.1-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Sun Jun 29 17:21:24 2014 ExecutablePath: /usr/lib/gcr/gcr-prompter InstallationDate: Installed on 2014-04-24 (66 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1335627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
Just do: sudo apt update sudo apt install linux-firmware sudo apt full-upgrade sudo reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Incomplete Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci0 24:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation --- ApportVersion: 2.20.1-0ubuntu2.15 Ar
[Touch-packages] [Bug 1781091] Re: notify-send only works the first time
To verify if this is a recent regression please download and reinstall the previous version: https://launchpad.net/ubuntu/+source/gnome- shell/3.28.1-0ubuntu2/+build/14791748 Does the problem then go away? ** Also affects: libnotify (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: libnotify (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1781091 Title: notify-send only works the first time Status in gnome-shell package in Ubuntu: Incomplete Status in libnotify package in Ubuntu: Incomplete Bug description: (I think this started happening after upgrading gnome-shell to 3.28.2-0ubuntu0.18.04.1 today.) Reproduce: * Run `notify-send ok ok`. Expected result: * A notification pops up for every execution of the command above. Actual result: * A notification might pop up every once in a while (it always appears the first time, I think). The journal gets a message like this for every notify-send call: Jul 11 02:29:20 tensin-pc1 gnome-shell[3723]: JS ERROR: Call to GetConnectionUnixProcessID failed: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ':1.68': no such name _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:71:26 I use notify-send in quite a few of my scripts, and it broke precisely today. > lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780995] Re: video drivers not working
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 Please explain in more detail what the problem is and what you see. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1780995 Title: video drivers not working Status in xorg-server package in Ubuntu: Incomplete Bug description: the intel video drivers not work in Dell optiplex 755 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 10 11:14:48 2018 DistUpgraded: 2018-07-09 20:33:32,337 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2018-04-06 (94 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. OptiPlex 755 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 12/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AF175320 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd12/09/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)
** Tags added: network -- 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/1781049 Title: WiFI hard blocked after resuming laptop (RTL 8723BE) Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781111] [NEW] libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-
Public bug reported: DRM package needed this lib, I installed it and DRM install proceeded successfuly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 Uname: Linux 4.14.0-041400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jul 6 19:18:35 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../libdrm-common_2.4.91-2~16.04.1_all.deb ... Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 DuplicateSignature: package:libdrm-common:2.4.91-2~16.04.1 Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-08-06 (338 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 8730w PackageArchitecture: all PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux pcie_aspm=force acpi_enforce_resources=lax intel_iommu=igfx_off quiet splash resume=/dev/ubuntu-vg/swap_1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.20 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU90728P0 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.20:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8730w dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.1-0~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 10 19:14:55 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 package-conflict ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/178 Title: libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 Status in libdrm package in Ubuntu: New Bug description: DRM package needed this lib, I installed it and DRM install proceeded successfuly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 Uname: Linux 4.14.0-041400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64
[Touch-packages] [Bug 1781111] Re: libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/178 Title: libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 Status in libdrm package in Ubuntu: New Bug description: DRM package needed this lib, I installed it and DRM install proceeded successfuly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 Uname: Linux 4.14.0-041400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jul 6 19:18:35 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../libdrm-common_2.4.91-2~16.04.1_all.deb ... Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 DuplicateSignature: package:libdrm-common:2.4.91-2~16.04.1 Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-08-06 (338 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 8730w PackageArchitecture: all PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux pcie_aspm=force acpi_enforce_resources=lax intel_iommu=igfx_off quiet splash resume=/dev/ubuntu-vg/swap_1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.20 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU90728P0 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.20:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8730w dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.1-0~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 10 19:14:55 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
TigrisAltaica from Ubuntu Forums has reported a similar issue on a HP Pavilion Laptop, unfortunately, renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa-base.bk didn't fix the issue. Here's the report: https://ubuntuforums.org/showthread.php?t=2396039 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1770290 Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) Status in openssh package in Ubuntu: Expired Bug description: bug ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 10 05:37:21 2018 DuplicateSignature: package:openssh-server:1:7.6p1-4 Setting up openssh-server (1:7.6p1-4) ... dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2018-02-17 (81 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: Upgraded to bionic on 2018-05-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781125] [NEW] Display drivers are not Avaialble
Public bug reported: I cannot see the displays listed in my display settings. Can't plugin an extra monitor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 11 10:53:54 2018 DistUpgraded: 2018-07-10 12:43:41,594 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d1] Subsystem: Dell Device [1028:07d1] InstallationDate: Installed on 2017-09-12 (301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0FH6CJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd03/08/2018:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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: Wed Jul 11 10:49:48 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1781125 Title: Display drivers are not Avaialble Status in xorg package in Ubuntu: New Bug description: I cannot see the displays listed in my display settings. Can't plugin an extra monitor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 11 10:53:54 2018 DistUpgraded: 2018-07-10 12:43:41,594 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d1] Subsystem: Dell Device [1028:07d1] InstallationDate: Installed on 2017-09-12 (301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.dat
[Touch-packages] [Bug 1781125] Re: Display drivers are not Avaialble
It appears the problem is that you have partially/unsuccessfully/manually installed the Nvidia graphics driver but it's no longer installed and it has left the 'nomodeset' flag in your kernel command line: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID =47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset which will prevent the default 'nouveau' graphics driver from working properly. To fix this you should edit your /etc/default/grub and remove 'nomodeset'. Then run 'sudo update-initramfs' and reboot. That will allow the nouveau driver to work properly. If that doesn't fully solve the problem then you can later also try the official nvidia driver by running: sudo apt install nvidia-driver-390 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1781125 Title: Display drivers are not Avaialble Status in xorg-server package in Ubuntu: Invalid Bug description: I cannot see the displays listed in my display settings. Can't plugin an extra monitor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 11 10:53:54 2018 DistUpgraded: 2018-07-10 12:43:41,594 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d1] Subsystem: Dell Device [1028:07d1] InstallationDate: Installed on 2017-09-12 (301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0FH6CJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd03/08/2018:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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: Wed Jul 11 10:49:48 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1781125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780807] Re: Please provide ED25519 support in 18.04 OpenSSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1780807 Title: Please provide ED25519 support in 18.04 OpenSSL Status in openssl package in Ubuntu: Confirmed Bug description: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have any support for it in the remaining lifetime of Ubuntu LTS released most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
