[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2015-01-17 Thread Alberto Salvia Novella
** 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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-12-22 Thread Bjoern Stuetz
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 Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-12-21 Thread arty
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-12-15 Thread rndmerle
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-11-09 Thread Ovidiu Manta
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-11-08 Thread Jacob Opstad
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-11-05 Thread Rob Dean
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-29 Thread M4he
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-28 Thread Christoph Erian
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 Desktop Bugs,

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-28 Thread Serhiy Zahoriya
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-27 Thread Mathias Dietrich
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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-25 Thread Davim
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 Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-24 Thread Davim
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]

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-24 Thread Daniel Crawford
Upgrading from 14.04 to 14.10. Only solution #62 worked. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-10-23 Thread Станислав
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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-09-14 Thread GiaBao Phu Truong
I don't have cairo-dock install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-09-04 Thread Mandeep Singh
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 Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title:

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-08-22 Thread Elisa
Solution #19 worked for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-08-17 Thread Paul BROWN
Another happy Solution #32 user here. THANKS!! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-08-17 Thread GiaBao Phu Truong
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-08-05 Thread Alurian Nighthawk
Can confirm Solution #32 working as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-07-27 Thread menner
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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-06-24 Thread Anders Hall
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-05-20 Thread Qu Bit
#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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-05-07 Thread Scott Talbert
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?).

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-29 Thread AtesComp
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-29 Thread AtesComp
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-28 Thread Dimitri Bakalow
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 -

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-27 Thread Alberto Salvia Novella
** 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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-27 Thread AtesComp
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-27 Thread AtesComp
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 *

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-27 Thread AtesComp
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 Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2014-01-27 Thread AtesComp
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-12-29 Thread locust
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-12-29 Thread locust
sorry , on an 64 bit system -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-12-14 Thread Launchpad Bug Tracker
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 Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-12-14 Thread Launchpad Bug Tracker
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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-12-14 Thread Magosányi Árpád
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-11-24 Thread OzzyFrank
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-11-23 Thread OzzyFrank
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

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-11-15 Thread A. Eibach
@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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

2013-11-13 Thread Serhiy Zahoriya
** 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 Desktop Bugs, which is subscribed to gdm in Ubuntu.

[Bug 1240336] Re: Not authorized to perform operation....

2013-11-12 Thread Serhiy Zahoriya
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu.