Lock Screen Server 12.10

[Colin Law]

On 6 February 2013 13:28, Oliver Grawert <ogra at ubuntu.com> wrote:
> hi,
> Am Mittwoch, den 06.02.2013, 14:16 +0100 schrieb Joep L. Blom:
>> >
>> > $ DISPLAY=:0 pkexec gedit /etc/fstab
>> > No protocol specified
>> > ** (gedit:8459): WARNING **: Could not open X display
>> > Cannot open display:
>> >
>> > Colin
>> >
>> >>
>> >
>> +1
>> I get exactly the same error as Colin (using Xubuntu on 12.04).
>> Joep
>>
> i discussed that with some colleagues and with upstream... seems pkexec
> supresses some variables:
>
> pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY gedit /etc/fstab

Yes, that works

>
> this line should work (though it is indeed awful, we might come up with
> a wrapper for this or just generally change all docs (they need to be
> touched anyway to reflect the change) to just recommend sudo ...)
>
> there is no reason for using gksu if you fire your app from an X
> terminal anyway, as there is no difference to sudo in functionality
> here ... apart from the graphical password prompt.

That is a surprise to me, I thought that on pain of <insert unpleasant
punishment/death> one should never use sudo for a graphical
application.  I read:

sudo uses user's profile and root's previledge.
gksu uses root's profile and root's previledge.

Some applications works fine, but some applications will *only* work
when your profile is root's profile. Especially, some gui-applications
need root's profile. And it is always much safer to use root's profile
when running root gui applications. (in order not to damage your users
profile environment)

gksu is not meant to run gui or cli applications, it is meant to use
the root profile, when you wan to use root profile you use gksu
instead of sudo, if your user profile is the same as your root profile
you will not notice much differences.

Colin

>
> ciao
>         oli
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>