Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1542782
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
I'm still on 18.04, but this problem remains for me, as well.
Grub with noresume doesn't work
RESUME=none doesn't work
RESUME=/dev/mapper/ubuntu-root doesn't work
RESUME=/dev/mapper/ubuntu-swap doesn't work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
When downgrading to the prior package, we do not see this problem.
We've taken the following steps as a work-around:
- apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1
- apt-get -y --allow-downgrades install
libsasl2-modules-db=2.1.26.dfsg1-14build1
- apt-get -y
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The
package itself is from the standard Ubuntu repos.
$ dpkg -s sssd
Package: sssd
Status: install ok installed
Priority: extra
Section: metapackages
Installed-Size: 32
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch:
I will try updating the packages to their current-released versions and
see if the problem persists. We ran into this issue across several 18.04
deployments yesterday, though. It prevented commands like `id -u
username` from working (at least that is how we initially noticed a
problem).
I'll
If I only install the latest packages (without the earlier versions of
these packages being installed previously) (i.e., if I do a clean
install of the most current packages when deploying a new host), it does
not work.
If I downgrade the packages to the prior versions, and then upgrade the
... I tried this following Leonidas' (leosilvab) request to "Could you
downgrade to the previous version and check if it happens there too? And
so re upgrade and re-test?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
After allowing the packages to be upgraded to their newer versions, the
problem does _not_ persist. We see expected / desired results.
We only get a good outcome after the packages have been upgraded,
though. When the packages are installed as the initial versions ... that
is when we consistently
Before I continue - I want to say thanks for your response to this
report. I appreciate your effort and help.
As for the issue, when I say, "If I only install the latest packages" I
mean a fully up-to-date system at the time of install, including sssd
version 1.16.1-1ubuntu1.4. As part of my
Public bug reported:
We are seeing the following in the journal after upgrading to these sets
of packages:
libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1
amd64
libsasl2-modules/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
We are doing additional testing here. Please sit tight / do not research
further until we check into things further on our end.
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in
In trying to recreate the issue this afternoon, it looks as though
installs based on all of the updated / most recent packages are
succeeding again (i.e., this may no longer be an issue).
In our dpkg logs, we noticed that an update came through today for libc-
bin (2.27-3ubuntu1), and wonder if
14 matches
Mail list logo
