Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

[!] ERROR #2-3: Can't find the WINE profile for Ruby v1.8.7 (/var/lib/veil/wine//drive_c/Ruby187/bin/ruby.exe). Run: /usr/share/veil/config/setup.sh --force --silent #489

Open
brutexploiter opened this issue Jan 6, 2023 · 3 comments

Comments

@brutexploiter
Copy link

Veil version

wine --version
wine-7.0.1 (Debian 7.0.1~repack-1)

OS Used - all info (architecture, linux flavor, etc)

Kali Linux (Windows Linux Subsystem)

0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0050:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0050:err:systray:initialize_systray Could not create tray window
0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0024:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
00fc:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00fc:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
[ERROR] Failed to install (Wine) Ruby.exe... Exit code: 1

image

@beyondsecurity
Copy link

beyondsecurity commented Feb 14, 2023

Hi,
Had the same issue on Kali Linux (2022.4), now solved! What's missing is the pyinstaller. If it's installed, the PATH was not set to global.

2 directories - they are different. Veil vs veil.

Remove current veil version:
sudo rm -r /var/lib/veil then follow steps below.

Step 1 - If pyinstaller not there, do the command: pip install pyinstaller
or if pyinstaller is there, do the command: pip install --upgrade pyinstaller
Reference: https://pyinstaller.org/en/stable/installation.html
Step 2 - Edit /.bashrc using either vim or nano. At end of file add the command:
export PATH="/Directory1:$PATH" - the PyInstaller on my machine was resided on /kali/home/.local/bin, so the command added on the .bashrc file in the home directory was:
export PATH="/home/kali/.local/bin:$PATH"
Reference: https://phoenixnap.com/kb/linux-add-to-path
Step 3 - Download Veil framework from github. Command issued was:
3.1 Go back to home directory. Command = cd ~/
3.2 Skip this step if Veil already downloaded otherwise command=
git clone https://github.com/Veil-Framework/Veil
Step 4
cd /Veil/ - go to the directory where Veil is downloaded
Next install veil. Command =
$ ./Veil/config/setup.sh --force --silent

Hope the above helps.

@ZouiedMarouan
Copy link

not working

@mothballs-x
Copy link

@marouanzed123

Was posted a while ago, but I just spent a day figuring this out so I thought I might as well respond, since there's no good answers in any of the posts on this.

  1. uninstall veil and dependencies with # sudo apt remove veil and # sudo purge veil or autoremove
  2. make sure that wine is installed ( #sudo apt install -y wine) and that 32bit architecture is enabled
    (# sudo dpkg --add-archtecture i386)
  3. Download veil again with apt
  4. To fix the pefile issue:
    open /usr/shared/veil/config/setup.sh with a texteditor. Change line 587 to:
    sudo -u "${trueuser}" WINEPREFIX="${winedir}" wine "${winedir}/drive_c/Python34/python.exe" "-m" "pip" "install" "-Iv" "pefile==2019.4.18"
  5. Run the setup like this (in root):

# DISPLAY=:0 /usr/shared/veil/config.setup.sh --force --silent

Wine doesn't seem to run correctly without DISPLAY set, as it needs to open the windows to run updates and configurations.
You can test it before running the veil setup file using # DISPLAY:=0 winecfg, which should run the wine configuration window.

I imagine that there's a way to set the display more permanently, but once the shell script runs you can open Veil without having to worry about it, since the problem is isolated to the install and doesn't affect the actual program.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants