OK, what's the deal with the display, anyway ?

The Ghost In The Machine ewill at lexideb.athghost7038suus.net
Thu Apr 26 13:43:02 CDT 2001

In comp.emulators.ms-windows.wine, Nix N. Nix
<nix at go-nix.ca>
on Thu, 26 Apr 2001 08:05:12 GMT
<3AE7D73E.9050606 at go-nix.ca>:

Try commenting out the

"Display" = ":0.0"


"Display" = "tux:10.0"


; "Display" = ":0.0"

in .wine/config , as I for one am not seeing this problem and can
bring up Borland C++ remotely (yes, it's slow, as I have a 56k :-) )

This might be a FAQ somewhere, but I can't say I know offhand.
I'm not seeing the problem, and my build is relatively current.

>Does anyone have a consistent way to set the display for wine programs 
>to /anything/ (meaning something other than :0.0)?  I have done the 
>ssh to the box I want to run the wine app from.
>(As a result, DISPLAY was set to "tux:10.0")
>I tried running
>wine ./notepad.exe
>from the Windows directory.  This gave me the following:
>Xlib: connection to ":0.0" refused by server
>Xlib: Client is not authorized to connect to Server
>Xlib: connection to ":0.0" refused by server
>Xlib: Client is not authorized to connect to Server
>err:seh:UnhandledExceptionFilter Couldn't start debugger 
>(debugger/winedbg 134623984 32) (2)
>Read the Wine Developers Guide on how to set up winedbg or another debugger
>err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 
>addr 0x400cd598
>It looks like it's trying to open :0.0 and, of course, it gets refused.
>Shouldn't it be trying to open tux:10.0 ?
>Now, interestingly, if I walk over to "tux" and I log in, then walk back 
>to my open ssh session and I re-type
>wine ./notepad.exe
>It starts building font metrics as if I had run it for the first time, 
>then notepad shows up.
>Why do I have to be logged in on :0.0 for wine to work on any other 
>display ?  I'd like to be able to simply set the DISPLAY (which I don't 
>have to, since ssh does it for me) and run
>wine ./notepad.exe
>without having to actually walk up to the machine (tux) and log in.
>Every other X app (xclock, rxvt, etc.) works over ssh, and connects to 
>the correct display, except wine.
>But wait, there's more !  Once, I managed to get wine to work properly 
>by editing my ~/.wine/config and adding
>"Display" = "tux:10.0" to the [x11drv] section.  This didn't work this 
>time, since I got the above error message again.
>Please, I'd really appreciate a consistent solution to this problem 
>since it has been plaguing me for some time.

ewill at aimnet.com -- insert random misquote here
EAC code #191       9d:19h:35m actually running Linux.
                    This is my other .sig.

More information about the wine-users mailing list