After release upgrade, the user looses permissions for several basic actions in the system
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | gdm (Ubuntu) |
Critical
|
Unassigned | ||
| | lightdm (Ubuntu) |
Critical
|
Unassigned | ||
| | lxdm (Ubuntu) |
Critical
|
Unassigned | ||
| | policykit-desktop-privileges (Ubuntu) |
Critical
|
Unassigned | ||
Bug Description
HOW TO REPRODUCE:
- Upgrade Ubuntu to the next release.
RESULT:
- The user looses permissions for several basic actions in the system.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: policykit-
ProcVersionSign
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
PackageArchitec
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: policykit-
UpgradeStatus: No upgrade log present (probably fresh install)
| Rob Frohne (frohro) wrote : | #1 |
| Rob Frohne (frohro) wrote : | #2 |
| Rob Frohne (frohro) wrote : | #3 |
I notice that I don't have any polkit-
| Rob Frohne (frohro) wrote : | #4 |
And trying to start the agent produces:
:~/.config/geany$ /usr/lib/
(polkit-
I don't see any polkit warning in my ~/.xsession-errors. It looks like this:
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
There is a post that has been somewhat helpful in thinking of things to try at:
http://
| Rob Frohne (frohro) wrote : | #5 |
I went looking for what starts the agent, and found it here:
test@frohro-
[Desktop Entry]
Name=PolicyKit Authentication Agent
Comment=PolicyKit Authentication Agent
Exec=/usr/
Terminal=false
Type=Application
Categories=
NoDisplay=true
OnlyShowIn=
X-GNOME-
AutostartCondit
X-Ubuntu-
I also checked my local ~/.config/autostart directory and there is nothing to start it there.
| Rob Frohne (frohro) wrote : | #6 |
I should also add that when I start the agent manually, it does not continue to run after the warning.
| Rob Frohne (frohro) wrote : | #7 |
Policykit seems to be working, at least this:
frohro@
==== AUTHENTICATING FOR org.freedesktop
Authentication is needed to run `/bin/echo' as the super user
Multiple identities can be used for authentication:
1. Rob Frohne,,, (frohro)
2. Rob Frohne,,, (frohro)
Choose identity to authenticate as (1-2): 2
Password:
==== AUTHENTICATION COMPLETE ===
test
| Launchpad Janitor (janitor) wrote : | #8 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in policykit-desktop-privileges (Ubuntu): | |
| status: | New → Confirmed |
| Dimitri Bakalow (dimitri-bakalow) wrote : | #9 |
Well... I am not sure, whether it will help or not, but I had two installations upgraded 13.04 -> 13.10.
One worked fine, other one got this very same problem. I am not completely sure, is this crude workaround or not, but I found help in this archlinux forum thread as all symptoms were the same.
https:/
To be exact - post #5 had the thing, that solved the problem - polkit-
Maybe this will provide some help...
| Dimitri Bakalow (dimitri-bakalow) wrote : | #10 |
Just a small addition - my problem was also present on login screen as it was not possible to issue shut down or restart command from there.
| Rob Frohne (frohro) wrote : | #11 |
HI Dimitri,
It is nice to have some company. I also note the same thing on the login screen. I have to shutdown by using the power key (not pushed a long time, though). Hopefully we can figure this out. I went so far as to look at the source code and found the warning message, and I probably need to go look at the source again. I couldn't find anything using Google, and I expect the folk that are experts on policykit-1-gnome are busy with bigger bugs to squash. And for that matter, this bug might be in policykit-1-gnome as well.
Rob
| Rob Frohne (frohro) wrote : | #12 |
Hi Dimitri,
How did you install Saucy? Did you do like I did, and install from DVD, then use dpkg to install the packages using dselect upgrade?
That might point to a problem with that method of installation.
Thanks,
Rob
I did upgrade 13.04 -> 13.10 and have the same problem. I can't mount usb,
install package via software center. Sound doesn't works too (not sure if
it's related).
Hope they will fix this soon.
Best regards,
Eduard
Best regards,
Eduard
On Sat, Oct 19, 2013 at 6:38 AM, Rob Frohne <email address hidden> wrote:
> Hi Dimitri,
>
> How did you install Saucy? Did you do like I did, and install from DVD,
> then use dpkg to install the packages using dselect upgrade?
>
> That might point to a problem with that method of installation.
>
> Thanks,
>
> Rob
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Not authorized to perform operation....
>
> Status in “policykit-
> Confirmed
>
> Bug description:
> 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-
> appears to be totally broken. Maybe someone can help me out.
>
> Thanks,
>
> Rob
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: policykit-
> ProcVersionSign
> 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
> PackageArchitec
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: policykit-
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https:/
>
I have this problem after an update from 13.04 to 13.10 on an 32bit system.
It does not work:
- SD-cards
- Shutdown via the menu, but with the power button
- Sound
- 3D-assalaration (Intel card)
| Dimitri Bakalow (dimitri-bakalow) wrote : | #15 |
Both of my installations were upgraded by means of Update Manager in usual way, however one of them did not show this problem. Both are 64-bit.
About this reference to previously mentioned archlinux thread - it looks quite obvious, that problem poassaibly had some relation to lightdm, because it was present without logging in (inability to chutdown or restart). This maybe screwed up user session with "no session for..." messages and no visible sessions for loginctl. This workaround fixed both problems.
| Rob Frohne (frohro) wrote : | #16 |
Well, Dimitri's solution in #9 above didn't help my situation, so maybe there are several causes of the same symptom. The /etc/pam.d/lightdm file I had in Ubuntu 13.04 is the same as what I started with in 13.10.
I am the original reporter of the bug#1241811; I have forced an update now (from command line, apt-get update, apt-get upgrade to bypass the staged upgrade) and it solved my problem. I am not sure if it's related to this, but you can try...
| Rob Frohne (frohro) wrote : | #18 |
I tried replacing /etc/polkit-1/ with the one from my Ubuntu 13.04 partition that works, but it didn't work.
I think this command helped me:
sudo pam-auth-update --force
I didn't change anything in dialog that appeared.
Best regards,
Eduard
On Sun, Oct 20, 2013 at 7:19 AM, Rob Frohne <email address hidden> wrote:
> I tried replacing /etc/polkit-1/ with the one from my Ubuntu 13.04
> partition that works, but it didn't work.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Not authorized to perform operation....
>
> Status in “policykit-
> Confirmed
>
> Bug description:
> 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-
> appears to be totally broken. Maybe someone can help me out.
>
> Thanks,
>
> Rob
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: policykit-
> ProcVersionSign
> 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
> PackageArchitec
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: policykit-
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https:/
>
| edbond (edbond) wrote : | #20 |
Well, it works for installing packages from software center (auth dialog
appears), still fails silently sometimes (for example when I try to remove
software source PPA).
I also created a new admin user, by running sudo gnome-control-
Users & Groups.
For that user everything works fine.
Best regards,
Eduard
On Sun, Oct 20, 2013 at 9:06 AM, Eduard Bondarenko <email address hidden> wrote:
> I think this command helped me:
> sudo pam-auth-update --force
> I didn't change anything in dialog that appeared.
>
> Best regards,
> Eduard
>
>
> On Sun, Oct 20, 2013 at 7:19 AM, Rob Frohne <email address hidden> wrote:
>
>> I tried replacing /etc/polkit-1/ with the one from my Ubuntu 13.04
>> partition that works, but it didn't work.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> Not authorized to perform operation....
>>
>> Status in “policykit-
>> Confirmed
>>
>> Bug description:
>> 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-
>> appears to be totally broken. Maybe someone can help me out.
>>
>> Thanks,
>>
>> Rob
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 13.10
>> Package: policykit-
>> ProcVersionSign
>> 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
>> PackageArchitec
>> ProcEnviron:
>> LANGUAGE=en_US
>> TERM=xterm
>> PATH=(custom, no user)
>> LANG=en_US.UTF-8
>> SHELL=/bin/bash
>> SourcePackage: policykit-
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https:/
>>
>
>
Thanks for the idea Eduard. It didn't work for me though.
| subdir (subdir) wrote : | #22 |
This worked for me
https:/
Thanks Eduard!
This fixed all of my problems i got after updgrade:
- slow unity (gallium-llvmpipe instead of intel driver)
- no sound
- unable to mount drives
- unable to connect to some networks
- unable to use vpn
etc etc etc...
| Geoff Hickey (ardri) wrote : | #23 |
Another vote for comment #19 - solved it for me too. (Thanks!)
I ran into this after a normal update-manager upgrade from 13.04.
Thanks!!. Comment #19 and a reboot restored functionality after updating to 13.10 via the gui..
| H.-Dirk Schmitt (dirk-computer42) wrote : | #25 |
#9 doesn't help me
I could resolve the problem (below gnome3) with the addition of the following policy file:
/etc/polkit-
[storage group mount override]
Identity=
Action=
ResultAny=yes
ResultInactive=yes
ResultActive=yes
| Manuel Martinez (maherma) wrote : | #26 |
Hi Dirk,
Thanks a lot, it's works for me.
| Manuel Martinez (maherma) wrote : | #27 |
Correction, only half works.
After create policy file, I'm able access from thunar to usb disk, create and delete files on it, but I can't umount it.
Manuel
NOTE: I have openbox as WM
| Rob Frohne (frohro) wrote : | #28 |
I needed to move on, so I gave up and re-installed the os without installing the same packages I had installed previously. The new install works fine, but I can't contribute to the bug report anymore. Sorry!
| H.-Dirk Schmitt (dirk-computer42) wrote : | #29 |
The following policy allows also the unmount and eject:
[Mounting, checking, etc. of internal drives]
Identity=
Action=
ResultAny=yes
ResultInactive=yes
ResultActive=yes
| Manuel Martinez (maherma) wrote : | #30 |
Hi Dirk,
+1 for your response #29.
USB disks are now fully functional and I can mount and unmount disks just before upgrade to 13.10.
Thanks. Regards
Manuel
| Luca Saba (lucasaba) wrote : | #31 |
+1 for #19 https:/
Thanks Eduard!
My desktop is now working again!
| Serhiy Zahoriya (xintx-ua) wrote : | #32 |
In my case #19 didn't work but appending
session required pam_loginuid.so
session required pam_systemd.so
to /etc/pam.d/lxdm fixed everything.
| BrainBug (brainbug0815) wrote : | #33 |
my story:
I use gdm + gnome and upgraded via upgrade manager from 12.10 => 13.04 and also from 13.04 => 13.10.
It worked for some weeks until a week ago. (GDM screen started but no loginwindow)
Switching to terminal (CTRL+ALT+F1) worked.
After a long search I found out that switching from gdm to lightdm brought me back into GUI Mode (sudo dpkg-reconfigure gdm => change to lightdm and reboot)
But then I found out I have permission problems like you described (Softwarecenter install/uninstall, updates, network, USB)
I tried a lot so I can't be sure what the solution was, but the last things I tried were:
#19
* (sudo pam-auth-update --force
* reboot
=> did not work
#23
* add
session required pam_loginuid.so
session required pam_systemd.so
to /etc/pam.d/gdm
* dpkg-reconfigure gdm (and select gdm)
* reboot
=> did not work (still no login window)
#23
* add
session required pam_loginuid.so
session required pam_systemd.so
to /etc/pam.d/lightdm
* dpkg-reconfigure gdm (and select lightdm)
* reboot
=> works! I can change network settings, install/uninstall packages, connect usb devices
#23
* try again "dpkg-reconfigure gdm" (and select gdm)
* (new lines in /etc/pam.d/gdm are already there from previous try)
* reboot
=> works!
I don't know why/how but now also gdm is working again
| Launchpad Janitor (janitor) wrote : | #34 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in lxdm (Ubuntu): | |
| status: | New → Confirmed |
| BrainBug (brainbug0815) wrote : | #35 |
sorry, typo and I have no idea how to edit my comment: #32 was probably the solution, not #23
| Dimitri Bakalow (dimitri-bakalow) wrote : | #36 |
If this bug is marked as confirmed for lxdm, then it must also be marked as such for lightdm as same workaround is applicable for both of them in case of a problem as seen in #33 - which was my case BTW.
Of course it depends on which display manager is used as only one can be in use at a time - Ubuntu has lightdm and Lubuntu has lxdm...
| summary: |
- Not authorized to perform operation.... + Not authorized to perform operation / Unable to determine the session we + are in: No session for pid |
| A. Eibach (andi3) wrote : Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid | #37 |
@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)
| OzzyFrank (ubuntu-ozzyfrank) wrote : | #38 |
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.
| OzzyFrank (ubuntu-ozzyfrank) wrote : | #39 |
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.
| Launchpad Janitor (janitor) wrote : | #40 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in gdm (Ubuntu): | |
| status: | New → Confirmed |
| Changed in lightdm (Ubuntu): | |
| status: | New → Confirmed |
| Magosányi Árpád (mag-magwas) wrote : | #42 |
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.
| locust (marineworks) wrote : | #43 |
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)
| locust (marineworks) wrote : | #44 |
sorry ,
.... on an 64 bit system
| 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 |
| AtesComp (atescomp) wrote : | #45 |
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/
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 optional pam_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.
| AtesComp (atescomp) wrote : | #46 |
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.
* 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.
* reboot
=> did not work
Tried version of #32
* modified to
session required pam_systemd.so
session required pam_loginuid.so
in /etc/pam.
* reboot
=> did not work
So nothing works so far.
| AtesComp (atescomp) wrote : | #47 |
My problem has something to do with KDE, udisk, and multiple authentication identities.
Disregard my prior comments.
| AtesComp (atescomp) wrote : | #48 |
OK, it is this issue. PolicyKit is choking udisk2. Here are the sample commands:
$ udisksctl mount -b /dev/sdm1 --no-user-
Error mounting /dev/sdm1: GDBus.Error:
$ udisksctl mount -b /dev/sdm1
==== AUTHENTICATING FOR org.freedesktop
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/
Since the " --no-user-
Once it's mounted, I can unmount normally.
The file /var/lib/
[Mounting, checking, etc. of internal drives]
Identity=
Action=
ResultActive=yes
We need something for the little guy to mount the external devices. Maybe a rule in /usr/share/
| Dimitri Bakalow (dimitri-bakalow) wrote : | #49 |
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.
| AtesComp (atescomp) wrote : | #50 |
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/
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/
/etc/
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.
| AtesComp (atescomp) wrote : | #51 |
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.
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.
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).
| Scott Talbert (swt-techie) wrote : | #52 |
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-
| Qu Bit (qbit-v) wrote : | #53 |
#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!
| Anders Hall (a.hall) wrote : | #54 |
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:/
| menner (menner) wrote : | #55 |
Solution #32 , appending
session required pam_loginuid.so
session required pam_systemd.so
to /etc/pam.d/lxdm
made everything work.
Thanks
| Alurian Nighthawk (howe20032003) wrote : | #56 |
Can confirm Solution #32 working as well.
| Paul BROWN (frozenzia) wrote : | #57 |
Another happy Solution #32 user here. THANKS!!
| GiaBao Phu Truong (2908bg) wrote : | #58 |
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.
| Elisa (elisa-algebra) wrote : | #59 |
Solution #19 worked for me. Thanks!
| Mandeep Singh (mandeeps708) wrote : | #60 |
GiaBao Phu Truong, I had this error I think this was due to the "cairo-dock". When I un-installed it everything was fine.
| GiaBao Phu Truong (2908bg) wrote : | #61 |
I don't have cairo-dock install.
| Станислав (jools333) wrote : | #62 |
For me the solution to the problem was the move to systemd. Like here http://
| Davim (davim) wrote : | #63 |
I got the same problem on upgrading from 14.04 to 14.10.
On dmesg I see:
[ 43.323648] systemd-
[ 43.323654] systemd-
[ 43.326729] systemd-
[ 43.326748] systemd-
[ 44.387104] init: plymouth-stop pre-start process (4632) terminated with status 1
[ 57.998337] audit: type=1400 audit(141419544
[ 57.998349] audit: type=1400 audit(141419544
[ 58.011666] audit: type=1400 audit(141419544
[ 67.951030] systemd-
[ 67.951036] systemd-
[ 67.953605] systemd-
[ 67.953621] systemd-
[ 67.956202] systemd-
[ 67.958750] systemd-
[ 76.073380] init: anacron main process (3189) killed by TERM signal
| Daniel Crawford (daniel-crawford) wrote : | #64 |
Upgrading from 14.04 to 14.10. Only solution #62 worked.
| Davim (davim) wrote : | #65 |
On upgrading from 14.04 to 14.10 only solution #64 worked:
sudo aptitude install systemd-sysv
| theghost (theghost) wrote : | #66 |
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 |
| Christoph Erian (kontaktwackler) wrote : | #67 |
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
| Serhiy Zahoriya (xintx-ua) wrote : | #68 |
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.
| M4he (mahe) wrote : | #69 |
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-
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:/
I then rebooted and got all functionality back. After reinstalling Skype and the libs and rebooting everything is still working fine.
| Rob Dean (rob-dean) wrote : | #70 |
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?
| Jacob Opstad (jeopstad) wrote : | #71 |
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.
| Ovidiu Manta (ovidiu-manta) wrote : | #72 |
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.
| rndmerle (rndmerle) wrote : | #73 |
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)
| arty (me-arty) wrote : | #74 |
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:/
| Bjoern Stuetz (bjoern-stuetz) wrote : | #75 |
Solution #74, i.e., removing ulatencyd worked for me. Thank you so much! I confirmed issue 1404653.
| description: | updated |
| summary: |
- 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: |
- 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 |
| no longer affects: | lightdm |
| Changed in gdm (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in lightdm (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in policykit-desktop-privileges (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in lxdm (Ubuntu): | |
| status: | Confirmed → Triaged |
| RDNielsen (rdnielsen) wrote : | #76 |
Removing ulatencyd also resolved the problem for me.
| Isabelle Andrade (isabelle-cda) wrote : | #77 |
Same problem with Ubuntu trusty after update. Tried the /etc/pam.d/lightdm solution, but did not work for me. I currently using network login with ldap, does it make a difference?
| Simon Déziel (sdeziel) wrote : | #78 |
I ran into this problem on Lubuntu 14.04. On that machine, the user created during the installation had no problem but every other regular users were affected.
The workaround was to join the regular users to the sudo group to please polkit. Since I really wanted those users to be "power less" I also added those sudoer rules:
jane ALL=(ALL) !ALL
jdoe ALL=(ALL) !ALL
| Changed in gdm (Ubuntu): | |
| assignee: | nobody → chaya (chaya-d-14) |
| Sourish Basu (sourish-basu) wrote : | #79 |
Made an account to say that #52 worked for me. After upgrading to Ubuntu 14.04 from 12.04, I had lost sound, the ability to shut down/reboot as a normal user, and the ability to mount external SD cards/hard drives. Did "sudo pam-auth-update --force" and "sudo apt-get remove --purge libpam-
I should say that at this point my pam.d is close, but not identical to, a fresh 14.04 install.
| tweej (tweej) wrote : | #80 |
Using solution from #32 requires the installation of libpam-systemd if you don't already have it. This package should be added as a dependency of lxdm if that ends up being the accepted fix.
| Владимир (vladimir-invest) wrote : | #81 |
I run into this problem after upgrade from Ubuntu 14.04 to Ubuntu 16.04
All suggested solutions didn't work well for me. But I found another very simple one.
I found the obsolete file in my home directory:
/home/current_
After removing it everything runs well.
i'm in 16.10 , i upgraded from 16.04 using dist-upgrade, well i'm facing same issue . can't access bunch of pendrive and android phone. :(
| Christophe Gras (christophe-gras) wrote : | #83 |
Got same issue after an upgrade from Ubuntu 14.04 to 16.04 and the following actions solved the problem :
sudo pam-auth-update --force
sudo vi/etc/
=> add following lines at the end :
session required pam_loginuid.so
session required pam_systemd.so
sudo reboot
| Changed in gdm (Ubuntu): | |
| assignee: | chaya (chaya-d-14) → nobody |
| tags: |
added: xenial removed: saucy utopic |
| Changed in policykit-desktop-privileges (Ubuntu): | |
| assignee: | nobody → Sushma Jain (sushma8j) |
| Changed in gdm (Ubuntu): | |
| assignee: | nobody → Shubham Lakshetti (laksh) |
| Shubham Lakshetti (laksh) wrote : | #84 |
Actually, it works for installing packages from software center (auth dialog
appears), still fails silently sometimes (for example when I try to remove
software source PPA).
I also created a new admin user, by running sudo gnome-control-
Users & Groups.
For that user everything works fine.
This appears to be a recurring bug which has been reported on Launchpad back in 2013. Every version of ubuntu since is affected by this but not everyone sees the error. On the moment I write this (march 2015) there's no permanent solution, however there are workarounds to solve the problem.
For Ubuntu 14.10 the problem appears to be related to the package ulatencyd. Removing this package causes the error to disappear in my situation. If I recall correctly I've installed this package manually on a certain moment in time so it does not belong to a standard install and therefore this might not affect everyone.
| Jackson Gregg (popit101) wrote : | #85 |
How do I gain the required privileges to edit the sudo document in /etc/pam.........
| Changed in gdm (Ubuntu): | |
| assignee: | Shubham Lakshetti (laksh) → nobody |
| Changed in policykit-desktop-privileges (Ubuntu): | |
| assignee: | Sushma Jain (sushma8j) → nobody |
I am in the sudo group and others:
~$ groups frohro
frohro : frohro adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse netdev lpadmin scanner vboxusers
I did find the policykit-1-doc package, but haven't found a configuration error (yet).