"Sorry, password authentication didn't work" after last update

Ask Fedora
,
1

Hi.

I’m having issue which I’m unable to diagnose as after the latest Fedora Silverblue 40 update I cannot login to my system - “Sorry, password authentication didn’t work”. If I rollback to 40.20240924, then I can login with the same password. Anyone having this ? Anyone found a solution to it ?

HW - Framework 13" AMD Ryzen 7040.
Unfortunately I cannot provide logs as I’m unable to login to the defective version.

Regards
ArtūrasB.

UPDATE: updated error message I get.

1 Like
2

Can you tell us the version number of the one that is not working? rpm-ostree status will get you that before you reboot for an update.

3

your keyboard layout might change during or after upgrade, for some reason

1 Like
4

To check this

  1. Always have passwords that are qwerty compatible, when possible. Saves a ton of hassle, like the one with LUKS which still isnt fixed
  2. Try to type it with qwerty layout, you can look its arrangement up online
5

oh man that problem made me install os’s two, three times :slight_smile: i even have alternative keys for my local ones and like u said, i create passwords according to qwerty one with these alternative keys :slight_smile:

1 Like
6

I have 2 passwords that are qwerty compatible by accident.

1 Like
7

Regarding qwerty compatible password - I have one as I made such mistakes in the past :wink:

8

The version which introduces the issue is 40.20241029.0

After rolling back to the previous one sudo journalctl -u gdm gives this error:

fedora gdm-password: gkr-pam: unable to locate daemon control file

and then

fedora gdm: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
fedora gdm: Gdm: Child process -1563 was already dead.
9

I wonder now if my issue and this are related

10

Is it possible to find information on what was changed/included to specific version of Workstation/Silverblue ?

11

Allright, I couldn’t find fix for my problem with the login loop, thus decided to do fresh install of Silverblue 41. This turned out quite good test on homed portability :wink:
First, backing up systemd-homed private and public keys together with the identity file to an external storage. As my home dir was on Framework’s external USB module, I simply unplugged it before I started the install. Next, installed fresh Fedora Silverblue 41, layered virt-manager+libvirt, copied systemd-homed private and public keys, identity file to its locations on the internal storage and plugged my USB module back to the laptop.
Now some clean up ;):

  • Had to adjust identity file,systemd-homed private and public keys permissions so only root can rw. Also chown said files to the root.
  • Enabled libvirtd.service
  • Added user to wheel and libvirt groups
  • Run restorecon on systemd-homed executables. Still required to do manually, but the good thing that homed policies are already included to the install base - kudos to @richiedaze :saluting_face: for enormous work adding homed SELinux policies to Fedora’s SElinux policy set.
  • Added homed authentication with authselect. I forgot to check if that was already fixed in the install and just ran the required command :smiley:
  • Added my Windows 11 Pro guest to virt-manager

Then rebooted, logged in with my homed-manager user et voila ! All my apps (I use Flathub remote added to user not system), settings, files are at my finger tips :sunglasses:

I truly believe that homed is the future of managing user files, settings and apps. Together with bootc it will make Linux Desktop available to non-technical users and will make the experience smoother. I know it’s not for everyone and will not solve all issues. But it is good. Once completed it might make migration from old PC to new one way less involving and tedious.

The case is closed :smiley:

2 Likes
12

There are no change logs published right now.