[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
** Description changed: - After a new install of 64 bit Ubuntu 13.10 on my second partition, I - used dpkg to reinstall all the same packages I had on my 32 bit 13.04 - partition. I copied all my home directory files over and updated all - the packages. I now find that I don't have permissions to change the - network settings; I can't mount my other hard drive or any USB stick - using nautilus, or (udisks without using sudo)' I can't run synaptic by - clicking on the GUI (I have to go to a terminal and sudo synaptic); etc. - I can't find any documentation on the configuration of policykit- - desktop-privileges, so I'm filing this bug. For me it appears to be - totally broken. Maybe someone can help me out. + HOW TO REPRODUCE: + - Upgrade Ubuntu to the next release. - Thanks, - - Rob + RESULT: + - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: - LANGUAGE=en_US - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Not authorized to perform operation / Unable to determine the session we are in: No session for pid + The user looses permissions for several basic actions in the system after release upgrade ** Summary changed: - The user looses permissions for several basic actions in the system after release upgrade + After release upgrade, the user looses permissions for several basic actions in the system -- 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: After release upgrade, the user looses permissions for several basic actions in the system 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Solution #74, i.e., removing ulatencyd worked for me. Thank you so much! I confirmed issue 1404653. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
In my case the deinstallation of ulatencyd has solved the problem. I had the problem in the old install, made a clean install and at some point started seeing the problem again. Somehow I guessed I should try deinstalling ulatencyd and it helped indeed. Installing it again and rebooting makes the problem appear again. I have reported the issue to ulatencyd as https://bugs.launchpad.net/ubuntu/+source/ulatencyd/+bug/1404653 -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I tried every single solution, even #69, and nothing worked for me. Not sure what I could try in order to help. I think, but I'm really not sure at all, that the issue started when I disabled the autologin feature from lightdm ; but I was reinstalling everything so I was doing a lot of different things :/ (indeed putting autologin back doesnt solve anything) -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I have just recently upgraded from 14.04 to 14.10 Ubuntu. I had this problem too, for an entire week now. couldn't edit users, network, suspend, shutdown, etc. tried every single solution to no avail. In the end i've repeated apt-get update/apt-get upgrade and it's fixed. Also fixed the pulseaudio sound problem i had and never figured out a solution for it. Linux desktop is a nice project, unfortunately riddled with bugs, and missing direction. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I'm also having this problem. I have just recently upgraded from 14.04 to 14.10 Ubuntu. I am wondering if this could in any way have to do with two administrator users on the same system. My system always has four users and two of them are administrators. I've never had anything like this happen before. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I'm having this problem on upgrade to Utopic (Kubuntu system) - ie unable to mount USB, clicking shutdown gets me to the login screen. I've tried appending session required pam_loginuid.so session required pam_systemd.so to /etc/pam.d/lightdm and rebooting but didn't fix the problem. Anyone have any other suggestions? -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Have had a similar issue. When I tried to run loginctl I got Failed to issue method call: Cannot launch daemon, file not found or permissions invalid and trying to execute polkit-gnome-authentication-agent-1 resulted in Unable to determine the session we are in: No session for pid None of the solutions above helped for me. What helped for me was to remove all i386 parts of PAM (which got installed with Skype) similar to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/comments/15 I then rebooted and got all functionality back. After reinstalling Skype and the libs and rebooting everything is still working fine. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Had same issues as described above (update manager - no privilege, shutdown/restart not working out of menu) after upgrade from 14.04 to 14.10. Following fixed everything: sudo apt-get install systemd-sysv -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
DO NOT INSTALL systemd-sysv unless you absolutely sure you know what you are doing. It breaks too much on 14.10 at the moment. There is a bunch of packages that need prerm/postinst script editing to not break dpkg state without upstart. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Same here on 14.10 coming from 14.04. I also updated the tags to reflect the affected releases. ** Tags added: trusty ** Tags added: utopic -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
On upgrading from 14.04 to 14.10 only solution #64 worked: sudo aptitude install systemd-sysv -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I got the same problem on upgrading from 14.04 to 14.10. On dmesg I see: [ 43.323648] systemd-logind[2817]: Failed to start unit user@111.service: Unknown unit: user@111.service [ 43.323654] systemd-logind[2817]: Failed to start user service: Unknown unit: user@111.service [ 43.326729] systemd-logind[2817]: New session c1 of user lightdm. [ 43.326748] systemd-logind[2817]: Linked /tmp/.X11-unix/X0 to /run/user/111/X11-display. [ 44.387104] init: plymouth-stop pre-start process (4632) terminated with status 1 [ 57.998337] audit: type=1400 audit(1414195441.914:38): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=4840 comm=apparmor_parser [ 57.998349] audit: type=1400 audit(1414195441.914:39): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=4840 comm=apparmor_parser [ 58.011666] audit: type=1400 audit(1414195441.930:40): apparmor=STATUS operation=profile_replace profile=unconfined name=third_party pid=4840 comm=apparmor_parser [ 67.951030] systemd-logind[2817]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 67.951036] systemd-logind[2817]: Failed to start user service: Unknown unit: user@1000.service [ 67.953605] systemd-logind[2817]: New session 1 of user ldavim. [ 67.953621] systemd-logind[2817]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 67.956202] systemd-logind[2817]: Existing logind session ID 1 used by new audit session, ignoring [ 67.958750] systemd-logind[2817]: New session c2 of user ldavim. [ 76.073380] init: anacron main process (3189) killed by TERM signal -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Upgrading from 14.04 to 14.10. Only solution #62 worked. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
For me the solution to the problem was the move to systemd. Like here http://askubuntu.com/questions/420917/how-can-i-replace-upstart-with- systemd -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I don't have cairo-dock install. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
GiaBao Phu Truong, I had this error I think this was due to the cairo- dock. When I un-installed it everything was fine. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Solution #19 worked for me. Thanks! -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Another happy Solution #32 user here. THANKS!! -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Have this on Ubuntu 14.10 Utopic. Try everything mentioned above but nothing work. When first start at the login screen, I can shutdown/ restart/ suspend by using the button at the top panel. After login to the account I have this bugs and can't shutdown/ restart/ suspend without 'sudo' command line. Logout to the login screen again, I lost the ability to shutdown/ restart/ suspend via the button at the top panel too. Reboot the system and everything happen again. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Can confirm Solution #32 working 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/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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Solution #32 , appending session required pam_loginuid.so session required pam_systemd.so to /etc/pam.d/lxdm made everything work. Thanks -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Comment 19 worked for me after reboot on 14.04. The error happened in relation to manual a password reset I did (replaced shadow and passwd with a backup). https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1240336/comments/19 -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
#29 finally worked for me on debian LXDE had a tried a fix before that used 'udisks' instead of 'udisks2' as well as some probably old action names. thanks! -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Experienced this problem on a machine after upgrading from 12.04 to 14.04. I compared my /etc/pam.d contents to a freshly installed 14.04 system. sudo pam-auth-update --force corrected most of the differences. Also uninstalled the libpam-ck-connector package (which seems to be not needed?). After doing this my /etc/pam.d matched the fresh system, and after logging out and back in, the problems went away. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Cleaned up /etc/pam.d and used sudo pam-auth-update and sudo pam- auth-update --force to autofix thing. I found I had an extra likewise PAM profile in /usr/share/pam-configs/. Nothing worked. Finally, I retried a previous solution: Tried version of #32 * Added session required pam_loginuid.so session required pam_systemd.so to top of /etc/pam.d/kdm Logout, Restart X, Login This worked. Mounting is fixed. System Settings-Login Screen reports You will be asked to authenticate before saving and it does indeed when I apply. I know that the order of selection is important to PAM, but I haven't yet compared my PAM files to a working system to find out where these entries really need to be placed. Why didn't I need them before the upgrade OR why where they removed on upgrade? The file dates seem to indicate that the PAM entries were not in the kdm file or @include chains before the update. Previous entries of pam_loginuid.so and pam_systemd.so via grep: /etc/pam.d/common-session:session optionalpam_systemd.so /etc/pam.d/sshd:sessionrequired pam_loginuid.so Since pam_loginuid.so is relegated to SSHD, it was never in the chain of PAM for a local login. The pam_systemd.so is third from the bottom in the common-session file. This is where I made my previous changes in #46. I'll do a few more tests. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I just tried a bit of surgery - I made a new installation (from the scratch) into Virtualbox and took all contents of /etc/pam.d and merged it into my main system - the one with this bug - thus overwriting files with new ones but keeping all additional files - not from the system itself - untouched. And guess what? Everything seems to work WITHOUT these workarounds tried before. This implies to the difference in some other file in /etc/pam.d, which is left over from 13.04 and causing this problem - other file than /etc/pam.d/lightdm. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
** Changed in: lightdm (Ubuntu) Importance: Undecided = Critical ** Changed in: lxdm (Ubuntu) Importance: Undecided = Critical ** Changed in: policykit-desktop-privileges (Ubuntu) Importance: Undecided = Critical ** Changed in: gdm (Ubuntu) Importance: Undecided = Critical -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I'm using Kubuntu and KDM. Updated to 13.10 (64bit, Kubuntu) and encountered the same problem. Cannot mount USB devices. Cannnot change settings in System Settings-Login Screen (apply and leave screen asks to apply again resulting in Unable to authenticate/execute the action: (code 4). Tried #19 * sudo pam-auth-update --force * reboot = did not work I haven't chacked the login screen shutdown problem. I'm looking at the PAM configurations and I have: session optionalpam_systemd.so in the common-session file, but don;t know why required would need to be set to make this work. Prior version are also optional. Will try it though. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Checked the login screen shutdown problem using KDM: this works. Reviewing the PAM files shows that the kdm file calls the common-session file. Tried version of #32 * modified to session required pam_systemd.so in /etc/pam.d/common-session * reboot = did not work Tried version of #32 * modified (reverted) to session optional pam_systemd.so added session optional pam_loginuid.so in /etc/pam.d/common-session * reboot = did not work Tried version of #32 * modified to session required pam_systemd.so session required pam_loginuid.so in /etc/pam.d/common-session * reboot = did not work So nothing works so far. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
My problem has something to do with KDE, udisk, and multiple authentication identities. Disregard my prior comments. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
OK, it is this issue. PolicyKit is choking udisk2. Here are the sample commands: $ udisksctl mount -b /dev/sdm1 --no-user-interaction Error mounting /dev/sdm1: GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation $ udisksctl mount -b /dev/sdm1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount 0c76 TS512MJFLASHA (/dev/sdm1) Multiple identities can be used for authentication: 1. Administrator (administrator) 2. User1 (user1) Choose identity to authenticate as (1-2): 2 Password: AUTHENTICATION COMPLETE === Mounted /dev/sdm1 at /media/user1/USB512MB. Since the --no-user-interaction command fails, users can't mount external devices without selecting a sudo user and password authenticatation. Once it's mounted, I can unmount normally. The file /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla contains (partial): [Mounting, checking, etc. of internal drives] Identity=unix-group:admin;unix-group:sudo Action=org.freedesktop.udisks.filesystem-*;org.freedesktop.udisks.drive-ata-smart*;org.freedesktop.udisks2.filesystem-mount-system;org.freedesktop.udisks2.encrypted-unlock-system;org.freedesktop.udisks2.filesystem-fstab; ResultActive=yes We need something for the little guy to mount the external devices. Maybe a rule in /usr/share/polkit-1/rules.d/ because System Settings-Removable Devices ain't git'in 'er done. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
sorry , on an 64 bit system -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I have this problem after an update from 13.04 to 13.10 on an 32bit system. It does not work: - SD-cards - USB disks - 3D-acceleration (Intel card) but if root login auto-mount does work I login through mdm (mint petra) -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm (Ubuntu) Status: New = Confirmed -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
This was the solution for me as well: sudo pam-auth-update --force Beware that it does change files in pam.d, so if you have a heavily customized pam configuration, prepare to be able to track the changes done, and fix things afterward. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Hi again. Solution #23 in comment #33 worked for me, so many thanks! For those who want to try it, here are the steps: gksu gedit /etc/pam.d/lightdm Under the first line #%PAM-1.0 paste the following: session required pam_loginuid.so session required pam_systemd.so ... then log out and back in again. If need be, run dpkg-reconfigure gdm and select lightdm (that was already selected in my case, so I don't know if OKing it actually made any difference). You shouldn't need to reboot, but do so if a simple logout doesn't do the trick. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Hi. I can confirm after upgrading to 13.10, there isn't much that my system says I'm authorised to do! Can't use Software Updater unless I invoke it with sudo from the terminal... I'm apparently not authorised to access any of my removable drives, or even the other partitions on my internal drive... I am not even allowed to play a DVD! (And not sure if it is related, but in case it is, it seems Shutdown no longer works, and I have to use the PC's power button). It's all the same mess in Unity, Gnome Shell, Gnome Classic (my preferred desktop), and KDE/Kubuntu. -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
@Dimitri Nope. I'm on Lubuntu Saucy and there's indeed lightdm running here (and _not_ lxdm). (Maybe it was lxdm on previous releases, which I didn't consider, though) -- 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
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
** Summary changed: - Not authorized to perform operation + Not authorized to perform operation / Unable to determine the session we are in: No session for pid -- 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
