Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: axehammer on 2012/11/18, 17:23:19
-
Greetings, I am not sure if this should be here or in bug fixes, but since I first noticed it after a dist-upgrade last night, I thought it may belong here.
I was unable to run partition manager as root. when I tried to run it this came up in a window.
Warning: You do not have administrative privileges.
It is possible to run KDE Partition Manager without these privileges. You will, however, not be allowed to apply operations.
Do you want to continue running KDE Partition Manager?
and it gave the option of running as a regular user or quitting. I tried running other GUI programs that required root access including gparted, synaptic, and krusader. None of which would run from the pull down menu or by terminal command. they would all ask for the root password, and then fail.
I have also tried adding my user name to the sudo group but using sudo does not seem to work any better.
-
Start these programs in a terminal as user
$ su-to-root -X -c gparted
Best regards,
Bequimão
-
You can also open KDE Menu Editor (we will use partitionmanager (KDE Partition Manager) for example)
Under General -> Command
The default setting is partitionmanager
Change that to kdesu partitionmanager
Then, top left corner and hit save,your system will update and your good to go
You can do that with any app
-
I have also tried adding my user name to the sudo group but using sudo does not seem to work any better.
Debian unlike Ubuntu does not come with sudo enabled by default.
As of debian squeeze, if you ask for the "Desktop task" during the installation , that pulls in sudo with a default configuration that automatically grants sudo-ing rights to any member of the sudo group
man sudo
-
For one-time use, or for something like kate which is needed for both user and root, press Alt-F2, enter "kdesu kate", enter the root password when prompted, and root is now running the package until you exit.
-
Is this a new install? I remember there could have been something with policykit on some Isos. Please have a look if polkit-kde-1 and policykit-1 are installed, reinstall them if necessary and try again.
-
Is this a new install? I remember there could have been something with policykit on some Isos. Please have a look if polkit-kde-1 and policykit-1 are installed, reinstall them if necessary and try again.
I build siduction with those included, it's still a no go, at least on my end here.