** 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 t
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 /
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
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
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
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 b
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
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 ...".
No
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 memb
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 su
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
Titl
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 / Unab
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 i
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] sys
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
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
T
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
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
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
l
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 ses
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 f
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
Tit
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 becau
#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/b
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?).
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/
2. Logout, Restart X, Login
3. Check that you can do it all.
4. Remove
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_login
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 - untouc
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
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 p
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
* mo
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
** 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
--
Y
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
Bu
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
T
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 mem
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 au
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:
No
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 i
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..
@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.launc
** 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.launchpa
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12
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 - Ub
sorry, typo and I have no idea how to edit my comment: #32 was probably
the solution, not #23
--
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
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxdm (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 a
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
In my case #19 didn't work but appending
session requiredpam_loginuid.so
session requiredpam_systemd.so
to /etc/pam.d/lxdm fixed everything.
** Also affects: lxdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification becaus
+1 for #19
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/comments/19
Thanks Eduard!
My desktop is now working again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The following policy allows also the unmount and eject:
[Mounting, checking, etc. of internal drives]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount;org.freedesktop.udisks2.eject-media;org.freedesktop.udisks2.power-off-drive;org.freedesktop.udisks2.ata-check-power;org.
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!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Dirk,
Thanks a lot, it's works for me.
--
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
To manage notifications about this bug go to:
https:/
#9 doesn't help me
I could resolve the problem (below gnome3) with the addition of the following
policy file:
/etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks2.filesystem-mount.pkla
[storage group mount override]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesyste
Thanks!!. Comment #19 and a reboot restored functionality after updating to
13.10 via the gui..
--
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
Another vote for comment #19 - solved it for me too. (Thanks!)
I ran into this after a normal update-manager upgrade from 13.04.
--
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 aut
This worked for me
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/comments/19
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 s
Thanks for the idea Eduard. It didn't work for me 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
To manage notifications about this bu
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 wrote:
> I tried replacing /etc/polkit-1/ with the one from my Ubuntu 13.04
> partition that works, but it didn't work
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-center ->
Users & Groups.
For that user everything works fine.
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240336
Title:
Not authorized to perform op
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...
--
You received this bug notification because you are a
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
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 w
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)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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 wrote:
> Hi
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 a member of Ubunt
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
n
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.
--
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
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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: policykit-desktop-privileges (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
Policykit seems to be working, at least this:
frohro@frohro-e6410:/media/bbfa3b46-995f-4d3f-bf61-ccbe04cfc84f/home/frohro/.config/autostart$
pkexec echo "test"
AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/bin/echo' as the super user
Multiple identit
I should also add that when I start the agent manually, it does not
continue to run after the warning.
--
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 operatio
I went looking for what starts the agent, and found it here:
test@frohro-e6410:/etc/xdg/autostart$ cat
polkit-gnome-authentication-agent-1.desktop
[Desktop Entry]
Name=PolicyKit Authentication Agent
Comment=PolicyKit Authentication Agent
Exec=/usr/lib/policykit-1-gnome/polkit-gnome-authenticatio
And trying to start the agent produces:
:~/.config/geany$ /usr/lib/policykit-1-gnome/polkit-gnome-
authentication-agent-1
(polkit-gnome-authentication-agent-1:5688): polkit-gnome-1-WARNING **:
Unable to determine the session we are in: No session for pid 5688
I don't see any polkit warning in my
I notice that I don't have any polkit-gnome-authentication-agent-1
process running, though there is a polkitd running.
--
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
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).
--
You received this bug notification
78 matches
Mail list logo
