Public bug reported:
On my System76 Gazelle, after doing a very specific sequence of
operations, I unintentionally got the system in a state where I would
reliably get "failed to refresh token" when trying to log in with the
correct password, which could only be worked around by turning on
airplane mode.
This is the sequence of steps that caused the issue to appear in the
first place, and it is reliably reproducible for me with these steps:
> Fully power off laptop. wait 10 seconds. boot machine without external
dock/monitors connected, log in, log into gnome keyring, connect
monitors, close lid, laptop should suspend. Open lid, press key, close
lid, try to log in. Fails with "Failed to refresh token" error.
It's not clear to me if this is specific to my hardware setup, but for
context, I typically have this laptop connected to a usb-c dock which is
driving 3 monitors and my keyboard+mouse. I think the bug is most likely
related to something to do with suspending, but I suspend this machine
pretty regularly without that sequence, and have not seen this issue
before doing those exact steps in that order.
This isn't really a major concern for me, as I don't normally do that
sequence of operations anyway (and it goes away after a reboot), but
figured it was worth a report, in case any other users have a more
precise reproducer.
I am also not yet completely certain if this is actually a bug in sssd,
or if it may originate from another part of the stack.
Only *known* to impact Noble, but may impact others as well.
** Affects: sssd (Ubuntu)
Importance: Low
Status: New
** Affects: sssd (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu)
Importance: Undecided => Low
** Also affects: sssd (Ubuntu Noble)
Importance: Undecided
Status: New
** Description changed:
On my System76 Gazelle, after doing a very specific sequence of
operations, I unintentionally got the system in a state where I would
reliably get "failed to refresh token" when trying to log in with the
correct password, which could only be worked around by turning on
airplane mode.
This is the sequence of steps that caused the issue to appear in the
first place, and it is reliably reproducible for me with these steps:
> Fully power off laptop. wait 10 seconds. boot machine without external
dock/monitors connected, log in, log into gnome keyring, connect
monitors, close lid, laptop should suspend. Open lid, press key, close
lid, try to log in. Fails with "Failed to refresh token" error.
It's not clear to me if this is specific to my hardware setup, but for
context, I typically have this laptop connected to a usb-c dock which is
driving 3 monitors and my keyboard+mouse. I think the bug is most likely
related to something to do with suspending, but I suspend this machine
pretty regularly without that sequence, and have not seen this issue
before doing those exact steps in that order.
This isn't really a major concern for me, as I don't normally do that
sequence of operations anyway (and it goes away after a reboot), but
figured it was worth a report, in case any other users have a more
precise reproducer.
I am also not yet completely certain if this is actually a bug in sssd,
or if it may originate from another part of the stack.
+
+ Only *known* to impact Noble, but may impact others as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146377
Title:
"Failed to refresh token" error on specific sequence of operations
involving suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2146377/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
