Re: lost ability to remote run sudo apps
Rodney D. Myers <rod_myers <at> fastmail.fm> writes:
>
> On 2/6/11 6:34 AM, Camaleón wrote:
> > On Sun, 06 Feb 2011 06:25:19 -0500, Rodney D. Myers wrote:
> >
> >> > On 2/6/11 6:00 AM, Camaleón wrote:
> >
> >>>>> >>> > sudo synaptic
> >>>>> >>> > X11 connection rejected because of wrong authentication.
> >>>>> >>> >
> >>>>> >>> > (synaptic:19563): Gtk-WARNING **: cannot open display:
> >>>>> >>> > localhost:10.0
> >>> >> (...)
> >>> >>
> >>> >> Try with "gksudo <app>"
> >>> >>
> >> >
> >> > okay, that worked.
> >> >
> >> > What's the difference?
> > I dunno the inners, but I guess it setups the rights to run X programs
> > under an X session. And not only for ssh but also for local sessions.
> >
> > Greetings,
> >
>
> Cool. thanks for the tip.
This happened to me on Fedora a few months ago. As best I can
tell, a recent sudo revision changed sudo default behavior.
sudo no longer uses the Xauthority cookies of the user invoking
sudo; instead it uses the root cookies, which don't correspond
to your ssh session.
If you haven't defined XAUTHORITY in your login profile (eg .bashrc
or whatever), set:
XAUTHORITY=$HOME/.Xauthority export XAUTHORITY
and add XAUTHORITY to one of the "Defaults env_keep" lines
in /etc/sudoers. (XAUTHORITY has been added to /etc/sudoers
in the current release of sudo.)
Reply to: