Hide Forgot
Description of problem: When new user is created in gnome-initial-setup rather than during installation and when he logs in for the first time, no polkit password window are appearing when they should and requests for password are immediately rejected. polkit starts working after relogin or reboot. Version-Release number of selected component (if applicable): polkit-0.113-5 How reproducible: Always. Steps to Reproduce: 1. Install Fedora 25 from live, not creating normal user during the process. 2. Create new user in gnome-initial-setup. 3. Log in as a newly-created user. 4. Try to use something that uses polkit to prompt for password (i. e. gnome-disks). Actual results: Polkit doesn't prompt user for his password. Expected results: Polkit should ask user for his password.
Reproduced. * gnome-disks is not running directly in a user session, but as a --gapplication-service under user@[$UID].service. So, the fallback logic from https://bugs.freedesktop.org/show_bug.cgi?id=78905 is activated. * gnome-initial-setup creates an "Type=x11" loginctl session first, then a "Type=wayland" session for the same user. * sd_uid_get_display() returns the "primary" = "first" session, and this session is used for gnome-disks. * OTOH, gnome-shell, and therefore the polkit password agent is registered in the wayland session, which was created later, and therefore does not match. * No agent is found, not passphrase is entered, access is correctly refused. Future logins create only a wayland session which contains the registered agent, so that agent is used and everything works. AFAICT, the way g-i-s creates two different sessions on the same VT is incompatible with how sd_uid_get_display() works. Or, perhaps, sd_uid_get_display() should be taught what "the display session” is in the x11+wayland session pair?
CCing Ray who knows a lot more about sessions than I do.
gnome-initial-setup runs under its own uid, so this is a little confusing to me. i'll need to reproduce to see what's going on.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.