Activating The Root Account (I Want To Use Su Not Sudo)

[GarryRicketson]

Yes, but this is Debian, NOT Ubuntu.
But to be honest, I don't know maybe it is another "new feature" added
to Debian as well, ????

[luvr]

Yes, but this is Debian, NOT Ubuntu.

Even so, the PolicyKit action really is “com.ubuntu.pkexec.synaptic”—so, yes, it must have been copied from Ubuntu.

[Dai_trying]

@Caitlin
Have you tried dpkg-reconfigure synaptic? it might give you the option again to use su instead of sudo although I haven't tested this.

[cfb]

As far as I know, the selection between "su" and "sudo" mode for "gksu" can be made either for the system or for the individual user. How to do it for the system has been described earlier in this thread:

Code: Select all

# update-alternatives --config libgksu-gconf-defaults
# update-gconf-defaults

.
To make the selection for the current user, use this command:

Code: Select all

$ gksu-properties

Now, I am quite certain that in Jessie, the user default mode for "gksu" was to use "su" mode. In Stretch I believe this has been changed to use the "sudo" mode. It may be in the documentation somewhere but I have simply noticed it.

[luvr]

@Caitlin
Have you tried dpkg-reconfigure synaptic? it might give you the option again to use su instead of sudo although I haven't tested this.

That was one of the things that I thought of too, but it doesn’t do anything, apparently.

[luvr]

To make the selection for the current user, use this command:

Code: Select all

$ gksu-properties

That must be it! It displays the “Privilege granting preferences” dialogue that Caitlin appeared to refer to earlier on.

[Caitlin]

Code: Select all

# gksu-properties

(gksu-properties:3744): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu-properties:3744): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu-properties:3744): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu-properties:3744): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running

--------------------------------------------------------------------------------------------------------------------------

# dpkg-reconfigure synaptic

(no output from this command)

--------------------------------------------------------------------------------------------------------------------------

# grep -r 'ubuntu' /etc/polkit-1 /var/lib/polkit-1 /usr/share/polkit-1

/usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy:  <action id="com.ubuntu.pkexec.synaptic">

In each case, I tried Synaptic again. No change.

Caitlin

[cfb]

You should run "gksu-properties" as your normal user, not as root.