On Sun, 2014-07-13 at 11:26 +0200, Guus Snijders wrote: > Op 13 jul. 2014 10:12 schreef "Ralf Mardorf" <ralf.mardorf@xxxxxxxxxxxxxx> > het volgende: > > On Fri, 2014-07-11 at 16:57 +0200, Guus Snijders wrote: > > > I haven't tested it, but xhost seems a bit superfluous in combination > > > with gksudo. Doesn't gksudo take care of setting the X auth itself? > > > > It doesn't. > > > > [rocketmouse@archlinux ~]$ gksudo -u chuser qupzilla > > [rocketmouse@archlinux ~]$ xhost + ; gksudo -u chuser qupzilla > > access control disabled, clients can connect from any host > > QupZilla: 0 extensions loaded > > [rocketmouse@archlinux ~]$ xhost - > > access control enabled, only authorized clients can connect > > Ok, so if you use gksudo and then launch an xterm, you get an display > error? Sounds a bit odd, for a gui to sudo... > (access control is more then just enabled/disabled ;-) ). You can use gksudo to launch xterm. [rocketmouse@archlinux ~]$ gksudo xterm Does open xterm with a root prompt. [rocketmouse@archlinux ~]$ gksudo -u chuser xterm Doesn't open xterm, no display error or any other output appears. [rocketmouse@archlinux ~]$ xhost + ; gksudo -u chuser xterm While running a X session by the user "rocketmouse" this will open xterm with a prompt for the user "chuser". Instead of xhost + you're free to use xhost a little bit smarter than I do.
