On Sun, Aug 13, 2006 at 20:15:23 +0200, Lubos Vrbka wrote:
> hi,
>
> >>>xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
> >>>
> >>>where "user" is the user that logged on to xdm. This will extract the
> >>>user's authorization cookie for the current display and merge it into
> >
hi,
xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
where "user" is the user that logged on to xdm. This will extract the
user's authorization cookie for the current display and merge it into
root's authority file. Then root should be able to access the display
until user log
On Sun, Aug 13, 2006 at 16:19:50 +0200, Lubos Vrbka wrote:
> hi,
>
> >One possibility is
> >
> >xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
> >
> >where "user" is the user that logged on to xdm. This will extract the
> >user's authorization cookie for the current display and
hi,
One possibility is
xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
where "user" is the user that logged on to xdm. This will extract the
user's authorization cookie for the current display and merge it into
root's authority file. Then root should be able to access the di
On Sun, Aug 13, 2006 at 15:16:16 +0200, Lubos Vrbka wrote:
> hi guys,
>
> this is probably some stupid mistake or omission i made...
>
> so far, i was starting X using the startx command (i.e., under ordinary
> user). recently i installed xdm to handle my logins (so X is now started
> under roo
hi guys,
this is probably some stupid mistake or omission i made...
so far, i was starting X using the startx command (i.e., under ordinary
user). recently i installed xdm to handle my logins (so X is now started
under root, i guess). everything works fine except that after login as
an ordina
On Fri, Mar 03, 2000 at 10:40:19AM -0900, Adam Shand wrote:
>
> > /usr/bin/X11/xauth: unable to open tmp file "/home/paul/.Xauthority-n"
> > /usr/bin/X11/xauth: unable to write authority file /home/paul/.Xauthority-n
> >
> > Is this potentially a permission problem? What should they be?
>
> i
> /usr/bin/X11/xauth: unable to open tmp file "/home/paul/.Xauthority-n"
> /usr/bin/X11/xauth: unable to write authority file /home/paul/.Xauthority-n
>
> Is this potentially a permission problem? What should they be?
i believe i just read a message in debian-user about there being a problem
> /usr/bin/X11/xauth: unable to open tmp file "/tmp/Xauthef4473-n"
> /usr/bin/X11/xauth: unable to write authority file /tmp/Xauthef4473-n
>
> and X11 forwarding does not work. This file (Xauthef4473-n) exists and has
> the following
> permissions:
> -rw---1 myname users
>
> Any id
Hi,
today I upgraded from slink to potato. Everything worked fine despite ssh.
I enabled X11 forwarding in ssh_config.
When I log from the potato box to another slink box everything works fine.
But when I ssh from a slink box into the potato machine I get a
/usr/bin/X11/xauth: unable to open t
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>I wish to thank all the responces which I received on my Xauthority problem. I
>went looking for 'ssh' when I read it in the thread, but wasn't able to find
>it in any package (bo system). Of note, I use the default 'bash' shell and
>chec
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the va
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the va
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the v
I wish to thank all the responces which I received on my Xauthority problem. I
went looking for 'ssh' when I read it in the thread, but wasn't able to find
it in any package (bo system). Of note, I use the default 'bash' shell and
checked the variables (as suggested) :
XAUTHORITY=~/.Xauthority
I
On Thu, 15 Jan 1998, Daniel Martin at cush wrote:
> "Jens B. Jorgensen" <[EMAIL PROTECTED]> writes:
>
> > Sir you are missing the point. Stop confusing the guy.
>
> Assuming, of course, that root never uses the xauth command.
I already got a mail from Jens containing phrases like "good point"
"Jens B. Jorgensen" <[EMAIL PROTECTED]> writes:
> Remco Blaakmeer wrote:
>
> > Don't do that. The minute root writes to that file (when root logs in to X
> > or uses the xauth command), it becomes owned by root and the user can't
> > log in to X anymore.
> >
> > What you could do is using ssh. Th
On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
> Sir you are missing the point. Stop confusing the guy. What you're
> saying is based upon an assumption that this trick would be used
> whenever root logged in. Now why would that be necessary? If you log
> into xdm as root you won't *need* to futz w
Remco Blaakmeer wrote:
> On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
>
> > Remco Blaakmeer wrote:
> >
> > > The solution is, of course:
> > >
> > > XAUTHORITY="${HOME}/.Xauthority"
> > > (AFAIK, $HOME is already set when /etc/profile is run)
> > >
> > > But this is the default location. I think
On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
> Remco Blaakmeer wrote:
>
> > The solution is, of course:
> >
> > XAUTHORITY="${HOME}/.Xauthority"
> > (AFAIK, $HOME is already set when /etc/profile is run)
> >
> > But this is the default location. I think it is better to not set the
> > variable a
Remco Blaakmeer wrote:
> On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
>
> > Miquel van Smoorenburg wrote:
> >
> > > In article <[EMAIL PROTECTED]>,
> > > <[EMAIL PROTECTED]> wrote:
> > > >I've chased this one for a while. Martin Bialasinski tried to help via
> > > >private
> > > >email, but nei
On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
> Miquel van Smoorenburg wrote:
>
> > In article <[EMAIL PROTECTED]>,
> > <[EMAIL PROTECTED]> wrote:
> > >I've chased this one for a while. Martin Bialasinski tried to help via
> > >private
> > >email, but neither of us could figure out what is wron
Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> <[EMAIL PROTECTED]> wrote:
> >I've chased this one for a while. Martin Bialasinski tried to help via
> >private
> >email, but neither of us could figure out what is wrong.
>
> >open("~/.Xauthority", O_RDONLY) = -1 ENOENT (
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>I've chased this one for a while. Martin Bialasinski tried to help via private
>email, but neither of us could figure out what is wrong.
>open("~/.Xauthority", O_RDONLY) = -1 ENOENT (No such file or directory)
>access("~/.Xauthor
I've chased this one for a while. Martin Bialasinski tried to help via private
email, but neither of us could figure out what is wrong.
# xauth -i generate westgac3/unix:0 .
xauth: creating new authority file ~/.Xauthority
xauth: unable to open tmp file "~/.Xauthority-n"
xauth: unable to write
25 matches
Mail list logo
