I use Debian Linux squeeze version wht KDE desktop. I installed wine and
am missing most of the destop stuff I have seen in the documentation. I
am getting the following when I run winecfg or wine control in my
command line console. The X server is definitely running since
everything in KDE works fine. Running echo $DISPLAY returns :0
No protocol specified
No protocol specified
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
What is $display supposed to return. Any suggestions for how to clear
this problem.
Gary R.
X server Display error in Debian Linux with KDE
X server Display error in Debian Linux with KDE
Gary Roach <[email protected]> wrote:
will normally be set to :0 or :0.0 in the (typical) situation where
the "client" (application, wine in this case) and the "server"
(display handler, usually xorg these days) are running on the same
system.
xterm or xclock) in the same console where Wine is failing? If
that produces the same result, you have a problem with X that has
nothing to do with wine; maybe your distro's support forum can
help.
You aren't by any chance trying to run wine as root? That is very
seldom a good idea.
$display (lower case) will normally be unset. $DISPLAY (upper case)I am getting the following when I run winecfg or wine control in
my command line console. The X server is definitely running since
everything in KDE works fine. Running echo $DISPLAY returns :0
No protocol specified
No protocol specified
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set
correctly.
What is $display supposed to return.
will normally be set to :0 or :0.0 in the (typical) situation where
the "client" (application, wine in this case) and the "server"
(display handler, usually xorg these days) are running on the same
system.
What happens if you try to run a "simple" X application (such asAny suggestions for how to clear this problem.
xterm or xclock) in the same console where Wine is failing? If
that produces the same result, you have a problem with X that has
nothing to do with wine; maybe your distro's support forum can
help.
You aren't by any chance trying to run wine as root? That is very
seldom a good idea.