Further testing indicates that the above (#50) solution can be removed
once you have a working system.
Steps:
1. Added
session required pam_loginuid.so
session required pam_systemd.so
to top of /etc/pam.d/<whatever_DM_file_you _use>
2. Logout, Restart X, Login
3. Check that you can do it all.
4. Remove
session required pam_loginuid.so
session required pam_systemd.so
from /etc/pam.d/<whatever_DM_file_you _use>
5. Logout, Restart X, Login
6. Check that you can STILL do it all.
After step 2, I ran through the usual group of crash reports for
submission after login. However, on the next login these crash reports
stopped occuring.
No reboot was performed until after step 6 to confirm the fix remained.
As a guess, the upgrade process needs to fufill some kind of rights
process that need these PAM lines during login to finish upgrading the
system. I tested that this also fixes usability for all other user
logins--after performing all steps for one user login, other user logins
work as well. So the fix seems to be a system wide correction that only
needs to be temporarily applied for a single login (probably requires a
user login who belongs to the admin/sudo group).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240336
Title:
Not authorized to perform operation / Unable to determine the session
we are in: No session for pid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
