Kali Linux-Wine-Display variable issues

JohnHWick · 05-17-2023, 12:26 PM

Hello all, Hope you are well.

Had an old Dell Latitude E5420 (Broken Screen, Hooked up to TV) laying around running a burnt out copy of
windows 7. I installed Kali linux on it and began trying to install some software for my school work. I'm install Veil and I'm having issues with the install script running the pop up window for wine.
I get the following errors:

Code:

002c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
002c:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."
0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0050:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."
0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 3
0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 14007
0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x800736b7
0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x800736b7
0050:err:ole:apartment_get_local_server_stream Failed: 0x800736b7
0050:err:ole:start_rpcss Failed to open RpcSs service
0040:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0040:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."
008c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
008c:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."

Quote:

"NOTE: Since the laptop running Kalie has a broken screen, I started xrdp service and im currently working on the machine via Remote Desktop on Windows 10"

After seeing the above error i opened a terminal and ran startx and see the followng:

Code:

X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux Kali-Attacker 6.1.0-kali9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1kali1 (2023-05-12) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-kali9-amd64 root=UUID=d445678a-08b8-4657-a0d1-6351b632295f ro quiet splash
xorg-server 2:21.1.7-3 (https://www.debian.org/support) 
Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed May 17 11:53:12 2023
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

I go and check what my display variable is set too by running

Quote:

echo $DISPLAY

on a terminal logged in as the default user "Kali" I see DISPLAY is set to :10.0, But when I run the command as root I see no DISPLAY variable at all:

Code:

┌──(root㉿Kali-Attacker)-[~]
└─# echo $DISPLAY

                                                                                                                      
┌──(root㉿Kali-Attacker)-[~]
└─# exit             
                                                                                                                      
┌──(kali㉿Kali-Attacker)-[~]
└─$ echo $DISPLAY
:10.0

even trying to run the installer as the "kali" user results in the same issue.

I should add that i tried adding a gnome desktop environment that kind of messed up the gui for the linux account. That may have something to do with it as well.

After Veil runs it checks this is what it finishes with:

Code:

[ERROR] Failed to run (wine) AutoIT.. Exit code: 255


[*] Finished AutoIT installation


[*] Settings already detected... Skipping...


[*] Finished environment checks

 [ERROR] There was issues installing the following:

 
Failed with installing dependencies (6): 0
Failed to install (Wine) Ruby.exe... Exit code: 1
Failed to run (wine) Ruby OCRA.. Exit code: 49
Failed to run (wine) AutoIT.. Exit code: 255



 [I] If you have any errors running Veil, run: './Veil.py --setup' and select the nuke the wine folder option

im at a lose and my troubles shooting skills in linux are not what they used to be. any help will be appreciated.

pan64 · 05-21-2023, 03:21 AM

First of all I have no idea why do you want to install wine on kali. It is not meant to run windows apps at all.
Next: https://www.linuxquestions.org/quest...ad-4175614092/

And actually yes, the DISPLAY variable "belongs" to the user who started the X session, not to root, that's why root has no DISPLAY set. You can configure your root account to access that display if you wish, but anyway you would need to choose another distro.
check for example here: https://www.linuxquestions.org/quest...ay-4175709671/

business_kid · 05-21-2023, 05:55 AM

Furthermore to what's already been said, it's very likely that a laptop defaults the $DISPLAY setting to the broken display in the Latitude. So one would expect display errors.

So you are using the Wrong OS on an unsuitable PC with a piece of software that particular OS should never see. Your poor results totally in line with our expectations. The matter really ends there. That is not something you fix. That is a situation where you stop wasting time and use your resources more wisely.