Re: vbox sid invalid mcookie
Liam O'Toole wrote: > I think something is broken in the terminal emulator. > > You are able to launch gnome-terminal itself > (presumably from the menu or the Alt-F2 dialog), Yes gnome-terminal menu // Alt-F2 lxterminal desktop icon // Alt-F2 xterm . desktop icon // Alt-F2 > but then something within that environment > is causing your problem. > > I suggest you try launching from xterm. > xterm no change, display problem persists $ xdpyinfo unable to open display "0:0" There is no problem launching X applications from the gnome menu, desktop icons, or Alt-F2 Attempts to launch X apps from either of 3 different terminal apps fails -- Stanley C. Kitching Human Being Phoenix, Arizona -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j0fqd3$md2$1...@dont-email.me
Re: vbox sid invalid mcookie
On 2011-07-22, Cousin Stanley wrote: > > Liam O'Toole wrote > >>> gdm should create .Xauthority for you, >>> without the need to manually do the xauth stuff. > > That's what I thought too > after reading the xauth man page > >"Normally xauth is not used > to create the authority file entry > in the first place; the program > that starts the X Server > ( often xdm or startx ) does that." > > However, testing in this particular context > doesn't provide either a new .Xauthority > file if one doesn't exist in my home dir > and doesn't provide an entry in an emply > .Xauthority file if I first create one > via touch > > I just re-tested to make sure > > o delete ~/.Xautority > o reboot or logout to restart X no difference > o A new .Xauthority file is not created > o No entries are added > to an empty .Xauthority file > > However, with an empty .Xauthority file > there is no invalid-magic-cookie message, > but disply // X server connection problems > > $ xdpyinfo > No protocol specified > unable to open display ":0.0" > > $ opera > No protocol specified > cannot connect to X server :0.0 > Connection refused > > $ gimp > > No protocol specified > Cannot open display > >>> You are talking about starting applications f >>> from a terminal emulator such as gnome-terminal, >>> and not from the console, right ? > > Right. > > The tests I just listed above > were done using gnome terminal > > If I now manually use xauth > to add the magic cookies into > an emplty .Xauthority file, > then they float up as invalid > whenever I try to start programs > as above I think something is broken in the terminal emulator. You are able to launch gnome-terminal itself (presumably from the menu or the Alt-F2 dialog), but then something within that environment is causing your problem. I suggest you try launching from xterm. If it works there, compare the output of the 'env' command in the two terminals. > > Perhaps if the X server display problem > is first straightened out then the xauth > magic cookie problem will fall into place > > Perhaps not > > Thanks a lot for the help and feedback > > I really appreciate it > No problem. Hope it helps. -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnj2l88r.5p0.liam.p.otoole@dipsy.tubbynet
Re: vbox sid invalid mcookie
Liam O'Toole wrote >> gdm should create .Xauthority for you, >> without the need to manually do the xauth stuff. That's what I thought too after reading the xauth man page "Normally xauth is not used to create the authority file entry in the first place; the program that starts the X Server ( often xdm or startx ) does that." However, testing in this particular context doesn't provide either a new .Xauthority file if one doesn't exist in my home dir and doesn't provide an entry in an emply .Xauthority file if I first create one via touch I just re-tested to make sure o delete ~/.Xautority o reboot or logout to restart X no difference o A new .Xauthority file is not created o No entries are added to an empty .Xauthority file However, with an empty .Xauthority file there is no invalid-magic-cookie message, but disply // X server connection problems $ xdpyinfo No protocol specified unable to open display ":0.0" $ opera No protocol specified cannot connect to X server :0.0 Connection refused $ gimp No protocol specified Cannot open display >> You are talking about starting applications f >> from a terminal emulator such as gnome-terminal, >> and not from the console, right ? Right. The tests I just listed above were done using gnome terminal If I now manually use xauth to add the magic cookies into an emplty .Xauthority file, then they float up as invalid whenever I try to start programs as above Perhaps if the X server display problem is first straightened out then the xauth magic cookie problem will fall into place Perhaps not Thanks a lot for the help and feedback I really appreciate it -- Stanley C. Kitching Human Being Phoenix, Arizona -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j0bt22$9o4$1...@dont-email.me
Re: vbox sid invalid mcookie
Liam O'Toole wrote: > That strongly suggests that the problem lies within the sid guest. > > How do you start X there? Usually one would use startx or a display manager, > launch a terminal within the session, and launch programs from the > terminal at will. I'm using gnome 2.30.2 and login through a gui so X must be started via gdm I've had this vbox sid guest on the same host for over 2 years and have had a few expected odd problems with sid that have eventually been fixed Until about a month ago I could always launch programs from the terminal at will until this invalid magic cookie problem began -- Stanley C. Kitching Human Being Phoenix, Arizona -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j03r8b$f5e$1...@dont-email.me
Re: vbox sid invalid mcookie
On 2011-07-18, Cousin Stanley wrote: > > Cousin Stanley wrote : > >>> Using a debian squeeze host for a Virtual Box 4.0.12 >>> debian sid guest, about a month ago I started having >>> invalid magic cookie problems when trying to do >>> anything X related from a terminal > > Liam O'Toole replied : > >> Are you running applications >> entirely within the Virtual Box guest ? > > Yes, just using it as a test-bed for sid > and for a few packages that are not in squeeze. > >> Or trying to forward output >> to the host display ? > > No, although I might want to try that > in the future > > > I can ssh & scp from the sid guest > to the squeeze host > > However, if I ssh -Y to the squeeze host > I get the invalid magic cookie message > the same as only trying to start a local > X program from the terminal in the sid guest > > X forwarding is enabled in the squeeze host, > and I can ssh -Y into the host > from ArchLinux and Ubuntu guests > also under VirtualBox on the same host > without problems > > That strongly suggests that the problem lies within the sid guest. How do you start X there? Usually one would use startx or a display manager, launch a terminal within the session, and launch programs from the terminal at will. -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnj2aekv.5p0.liam.p.otoole@dipsy.tubbynet
Re: vbox sid invalid mcookie
Cousin Stanley wrote : >> Using a debian squeeze host for a Virtual Box 4.0.12 >> debian sid guest, about a month ago I started having >> invalid magic cookie problems when trying to do >> anything X related from a terminal Liam O'Toole replied : > Are you running applications > entirely within the Virtual Box guest ? Yes, just using it as a test-bed for sid and for a few packages that are not in squeeze. > Or trying to forward output > to the host display ? No, although I might want to try that in the future I can ssh & scp from the sid guest to the squeeze host However, if I ssh -Y to the squeeze host I get the invalid magic cookie message the same as only trying to start a local X program from the terminal in the sid guest X forwarding is enabled in the squeeze host, and I can ssh -Y into the host from ArchLinux and Ubuntu guests also under VirtualBox on the same host without problems -- Stanley C. Kitching Human Being Phoenix, Arizona -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j02asc$b22$1...@dont-email.me
Re: vbox sid invalid mcookie
On 2011-07-17, Cousin Stanley wrote: > > Using a debian squeeze host for a Virtual Box 4.0.12 > debian sid guest, about a month ago I started having > invalid magic cookie problems when trying to do > anything X related from a terminal (...) Are you running applications entirely within the Virtual Box guest? Or trying to forward output to the host display? Or something else? -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnj295ld.5p0.liam.p.otoole@dipsy.tubbynet
