I had no idea of the mess I was creating by simply doing an install of Wheezy without a root account. I just assumed that if I was being given the option to setup Debian this way that it was ok to do so??? Silly me?
Actually this messed me up three times. I am creating three Debian system setups out of 6, to create remasters out of.
Gnome 3 has me doing a lot of extra work attempting to create as nice a desktop as I had with Gnome 2.
I am making Debian-Mate only, a Debian-Cinnamon only and Debian-Xfce only, custom setups to, hopefully, remaster.
I am also currently creating Mint13-Mate only, Ubuntu-Mate only and Xubuntu, custom setups to hopefully remaster.
Gnome 3 stuff is messing with the Mate desktops, and upgrades to Mate 1.6 destroyed all my custom setups, and my already created remasters are now useless; as soon as they are installed and then upgraded, they too loose there custom desktop. Grrrrrrr!
Anyway, I am having issues with Debian setups with no root account. Some software asks for the root password, which doesn't exist.
Finally I found your post and have some idea what to do. At first I followed your instructions, but found there was more to the story, and then had to undo your instructions to have a better look. Clearly there are some things missing from your instructions, although they are the best I have found. I think you will be able to make more sense of my setup questions than anyone else...I hope.
I set aside Debian-Mate for now. Haven't got a single remaster to go according to plan as yet. Same with Mint-Mate and Ubuntu-Mate.
Both Debian-Cinnamon and Debian-Xfce setups, had similar difficulties with software asking for the non existent root password.
Some applications merely needed gksudo added in the Menu command lines and I am now asked for my user password, as I foolishly expected would be setup when I installed them. I managed to fix most of them using gksudo.
Dealing with Wheezy-Xfce for the moment as it seems to have the best chance of recreating my custom style desktop. Probably would be done already if not for doing a user only installation; not sure why I did that just now??? I guess I thought that would be simpler. Hmmmmm.
Anyway, while following your instructions I noticed that there were already some xml files in /usr/share/polkit-1/actions
Specifically there are entries there already for Synaptic and GParted along with 14 more entries.
Here is the entry for Synaptic:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
<message>Authentication is required to run the Synaptic Package Manager</message>
<message xml:lang="ru">Для запуска менеджера пакетов Synaptic требуется аутентификация</message>
Your instructions also include an entry for Synaptic, and I was not being asked for a root password to run it; just my user password. Seeing as how it wasn't broken, I undid your suggested changes to get better informed.
I installed lxmed "Main Menu Editor", so I could fix up all the applications, that did ask for a root password. In fact lxmed also asked for a root password; so I had to start lxmed with a terminal- gksudo lxmed, and then I added gksudo to the command line within lxmed - (Main Menu Editor); now that lxmed was running.
Now that I had a working Menu Editor, that was for some unknown to me reason, not included in Xfce, I was able to fix GUFW and Gdebi so that I only needed my user password. Your instructions also worked to start GUFW and Gdebi by putting- gksudo pkexec in front of the start up commands, within the Menu Editor(lxmed).
I got scared though when I noticed that the startup commands were not all the same. Synaptic and GParted use synaptic-pkexec and gparted-pkexec, and these command lines remain, after undoing your instructions, and both apps work as they did when installed; user password for administrative type job. I have to assume that the reason that they worked is due to there preexisting entries into the /usr/share/polkit-1/actions folder.
Long story, I know, but I like to be clear. This is what has me stumped and stopped my next attempt to remaster a beautiful Debian-Xfce setup IMHO:
I noticed that in your instructions, at the beginning of this forum thread, there is a section for <action id="org.freedesktop.policykit.pkexec.run-remsu">
And you also added an entry to run remastersys!
I also noticed that Remastersys Backup had the startup command- remsu /usr/bin/remastersys-gui
I wasn't having any luck with gksudo remsu or sudo remsu or pkexec remsu or gksudo pkexec remsu or /usr/bin/remastersys-gui-pkexec???? After using your instructions.
I could, however, remove the remsu and simply change the menu line to: gksudo /usr/bin/remastersys-gui and Remastersys started, apparently fine, with my user password.
Now to my questions- that took awhile, what?
Is it ok to remove the remsu from:
remsu /usr/bin/remastersys-grub-restore gui
and replace it with gksudo? And! Will remastersys be able to do its' job with these changes to the startup commands? Or is there a better, or necessary, way to do this with PolicyKit?