Warning wine cmd exe c echo appdata returned empty string error message

Не могу запустить wine

Установлен wine64 version 5.0.4 при помощи pkg install wine

При запуске exe файла вылетает с ошибками в консоли:

not supported on this system

что дальше? на haiku или на kolibrios игоры запускать будете?

То есть мне нужно искать какие-то нативные чтобы запустилось?

Под 6.0.1-вайном они же запускаются, я проверял

wine64 version 5.0.4 при помощи pkg install wine

такое нужно самому компилять из портов

Компилять нужно только mesa и всё что связано с видео, wine и i386-wine — совершенно необязательно.

bambie , я не знаю что ты хочешь запустить, но ты уверен что оно именно PE32+ (x86-64), запуская его через wine (amd64)?

а что, у вас там есть уже собранный wine с esync патчем?

ты уверен что оно именно PE32+ (x86-64), запуская его через wine (amd64)?

Я могу в этом убедиться только запустив его с 32битным wine:

mesa и всё что связано с видео

mesa не компиляю — только видеодрайвера

С помощью file можно посмотреть:

Был не прав, оно действительно было PE32

Kron4ek , спасибо большое.

как удалить старое ядро? было у меня оно одно, но подвезли новый drm-kmod который со старым ядром отказался работать, пришлось собрать новое ядро и установить в него новый drm-kmod — теперь у меня два ядра, но старое не нужно — как его удалить? может есть какое нибудь remove-old-kernels или что то типа такого?

А что, из портов можно собрать wine с esync? (%

Еще вопрос. Могу ли я установить второй вайн, собрав его с другим PREXIF? Если да, то как?

с другим PREFIX

Я могу в этом убедиться только запустив его с 32битным wine

file -b /path/to/file.exe

Сам понимаешь, телепаты в отпуске. (%

Был не прав, оно действительно было PE32

FreeBSD хранит только два ядра — последнее и предыдущее, каждый make installkernel перемещает /boot/kernel в /boot/kernel.old (и удаляет старый /boot/kernel.old , если он существует), затем ставит новое в /boot/kernel .

А вот что происходит с /boot/modules я не помню, при обновлении GENERIC на следующий релиз оно вайпает чуть ли не всю систему.

Тебе не обязательно собирать wine с другим PREFIX, достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Могу поделиться скриптом, но он во-первых нифига не документирован (могу на пальцах объяснить что как, но никакой поддержки не обещаю, об этом дальше), а во-вторых не работает с wine >=6.0 (там что-то с окружением, гуглить сейчас лень, фиксить не планирую, ибо проще переписать скрипт с нуля, там костылей за два года быстроправок скопилось).

а что, у вас там есть уже собранный wine с esync патчем?

А что, на фряхе появился eventfd?

UPD: Фигасе, The eventfd() system call first appeared in FreeBSD 13.0.

Все, фря готова для гейминга

Есть же всякие гуи вроде PlayOnLinux, они не умеют рулить несколькими версиями вайна?

Есть форк — PlayOnFreeBSD, но я никогда его не тыкал. А вот Lutris на FreeBSD судя по всему вообще не работает (нет никаких упоминаний на официальном сайте, никаких упоминаний на официальном форуме FreeBSD и на сабреддите).

Мне проще накидать скрипт на двадцать пять килобайт и пару лет не париться по этому поводу. Причём в эти двадцать пять килобайт бонусом влезла поддержка dosbox, renpy, gzdoom, pcsxr и dolphin-emu как для amd64, так и для i386.

…достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Хочу узнать об этом поподробнее. Как это сделать?

Могу поделиться скриптом, но он во-первых нифига не документирован (могу на пальцах объяснить что как, но никакой поддержки не обещаю, об этом дальше), а во-вторых не работает с wine >=6.0 (там что-то с окружением, гуглить сейчас лень, фиксить не планирую, ибо проще переписать скрипт с нуля, там костылей за два года быстроправок скопилось).

Пожалуй, давай, это лишним не будет. В инете информации по этому поводу мало, а этот вопрос может быть интересен не только мне. Ну и если проще переписать, может быть кто-то подскажет, кому будет не лень? А так я не против в этом разобраться.

Есть же всякие гуи вроде PlayOnLinux

https://www.freshports.org/emulators/playonbsd Если это оно, то он удален, написано в прошлом году. Но всё равно это было просто обёрткой для wine

Мне проще накидать скрипт на двадцать пять килобайт и пару лет не париться по этому поводу.

Еще проще — установить games/homura.

…достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Хочу узнать об этом поподробнее. Как это сделать?

Нужно понимать как устроено окружение и что нужно конкретному приложению для полноценной работы.

Если раскуришь скрипты многоуважаемого Kron4ek , многое поймёшь конкретно про Wine. Мой скрипт местами переусложнён и/или сильно несовершенен, но он никогда не пилился для публичного использования, потому он такой какой он есть.

Пожалуй, давай, это лишним не будет.

Ссылка в конце комментария.

В инете информации по этому поводу мало, а этот вопрос может быть интересен не только мне. Ну и если проще переписать, может быть кто-то подскажет, кому будет не лень? А так я не против в этом разобраться.

Ну, FreeBSD никогда не позиционировалась как игровая платформа, потому готовых решений до сих пор нет, а все попытки быстро загибаются.

Я не особо геймер, потому не пытался сделать что-то с планами на будущее.

Внутри быстро накиданный README, наверняка с кучей очепяток и ошибок, но в общих чертах должно быть понятно. А если нет — задавай свои ответы, завтра (если повезёт) гляну.

Источник

Error While installing: warning: wine cmd.exe /c echo ‘%AppData%’ returned empty string, error message «» #226

I’m fairly new to github and linux in general, apologies in advance.

**Description: **
After running ‘lutris -i Downloads/modorganizer2.yml’, installation does not complete. The full log is here, https://pastebin.com/QYVjkuCr; below I have copied the most recent messages. I was able to install mod organizer twice before, but I uninstalled MO2 trying to get the dialogue in Skyrim SE to work, and have not been able to reinstall. For what it’s worth, I haven’t run into the issues described in #61 this time around.

System Info:
OS: Drauger OS (Ubuntu 20.04 focal)
Wine Version: wine-6.0.1
Winetricks Version: 20210206-next — sha256sum: 75730c54ef76da9109f48a064bc53c61bb7301d690ab74fd3c23c719d1683de9

Terminal Output:
warning: wine cmd.exe /c echo ‘%AppData%’ returned empty string, error message «»
———
Monitored process exited.
Initial process has exited (return code: 256)
All children have exited.
Exit with returncode 256
2021-06-17 22:04:16,669: I can’t move /home/kyle/.cache/lutris/installer/mod-organizer-2/successful-prefix-preparation, it does not exist
None
2021-06-17 22:04:16,669: Error while completing task >: I can’t move /home/kyle/.cache/lutris/installer/mod-organizer-2/successful-prefix-preparation, it does not exist
None
File «/usr/lib/python3/dist-packages/lutris/util/jobs.py», line 34, in target
result = self.function(*args, **kwargs)
File «/usr/lib/python3/dist-packages/lutris/installer/commands.py», line 283, in move
raise ScriptingError(«I can’t move %s, it does not exist» % src)
2021-06-17 22:05:04,901: Cancelling installation of Mod Organizer 2

The text was updated successfully, but these errors were encountered:

Источник

Warning wine cmd exe c echo appdata returned empty string error message

Post by jstromsoe » Mon Apr 04, 2022 11:42 pm

Having some issues building Wine (stable branch, cloned from c7c729c0db7c3e246182a890de4c606f3e394d0e).

Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy

I’m building Wine from scratch because as of this writing there is no build for jammy (it’s brand new).

I’m able to successfully build for 64 bit Wine using:
«`
cd

/wine-dirs/wine64-build/
../wine-source/configure —enable-win64
make
«`
When I try to build for 32 bit (2nd part of instructions)
«`
cd

/wine-dirs/wine32-build/
PKG_CONFIG_PATH=/usr/lib32 ../wine-source/configure —with-wine64=../wine64-build
make
«`

I make it pretty far into the compile but it errors out on :
«`
gcc -m32 -o dlls/capi2032/capi2032.so -shared -Wl,-Bsymbolic -Wl,-soname,capi2032.so -Wl,-z,defs dlls/capi2032/unixlib.o dlls/ntdll/ntdll.so
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_isinstalled’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:117: undefined reference to `capi20_isinstalled’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_profile’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:112: undefined reference to `capi20_get_profile’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_serial_number’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:105: undefined reference to `capi20_get_serial_number’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_version’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:93: undefined reference to `capi20_get_version’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_manufacturer’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:85: undefined reference to `capi20_get_manufacturer’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_waitformessage’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:78: undefined reference to `capi20_waitformessage’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_message’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:71: undefined reference to `capi20_get_message’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_put_message’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:63: undefined reference to `capi20_put_message’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_release’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:56: undefined reference to `capi20_release’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_register’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:48: undefined reference to `capi20_register’
collect2: error: ld returned 1 exit status
«`

Anyone have any ideas ? Any help super appreciated.

Re: Wine Build on Ubuntu 22.04

Post by jkfloris » Tue Apr 05, 2022 6:13 pm

A few things you can try:
— Build without PKG_CONFIG_PATH=/usr/lib32
I believe the gstreamer problem is solved in newer versions.

— Build without CAPI (Do you need ISDN support?)

Re: Wine Build on Ubuntu 22.04

Post by jstromsoe » Tue Apr 05, 2022 10:32 pm

Sooo close. I ran again with —without-capi and that got much further into the compile. I believe per the instructions you NEED to specify PKG_CONFIG to a 32 bit set of libraries or none of what’s being attempted with WoW (32 bit support win apps) would be accomplished. So I left that as you can see, but got another compiler error. Do I need to go install a 32 bit gstreamer version? If so, which and what dependencies? Thanks in advance!

Источник

Warning wine cmd exe c echo appdata returned empty string error message

Post by dE_logics » Thu Nov 10, 2011 5:16 am

I’m trying to install a program using winetricks, but I’m using a separate wine install and WINEPREFIX, I run any command as such —

WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

On the other hand —

WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ‘/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine’ cmd

C:>echo %ProgramFiles%
C:Program Files

Post by dimesio » Thu Nov 10, 2011 10:58 am

Post by dE_logics » Thu Nov 10, 2011 11:44 am

I tried that, it doesn’t matter —

WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine’ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks
——————————————————
/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine cmd.exe /c echo ‘%ProgramFiles%’ returned empty string
——————————————————

Post by dE_logics » Thu Nov 10, 2011 11:52 am

WINEPREFIX=/home/de/media_writeit!/temp(others)/walkthrough/ /home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine cmd.exe /c echo ‘%ProgramFiles%’

Post by dimesio » Thu Nov 10, 2011 2:40 pm

Post by dE_logics » Thu Nov 10, 2011 10:08 pm

Nothing will happen (and nothing happened), winetricks is only available in the current directory, so it says command not found.

WINEPREFIX=’/home/de/game/temp(game)/soundforge-10′ ./winetricks
——————————————————
wine cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by dimesio » Thu Nov 10, 2011 11:35 pm

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by DanKegel » Fri Nov 11, 2011 12:13 am

dE_logics wrote: WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

WINE is how you tell winetricks which wine to run.

WINEPREFIX is how you tell wine (and winetricks) where the fake C drive and
registry live.

Do you really have two versions of wine? What program are you trying to install?

(Dimesio: The ./ in front of winetricks is for when you’ve downloaded winetricks yourself
and not installed it, but have marked it executable.
If you haven’t marked it executable, you have to use ‘sh winetricks’.
If you use the winetricks installed by your distro, you don’t want the ./ or the sh.
This is all about how the shell searches for commands in the directories
listed in the PATH environment variable.)

Post by dE_logics » Fri Nov 11, 2011 1:40 am

dE_logics wrote: WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

WINE is how you tell winetricks which wine to run.

WINEPREFIX is how you tell wine (and winetricks) where the fake C drive and
registry live.

Do you really have two versions of wine? What program are you trying to install?

Yes, this system is 64 bit and this problem exists when you try running a 64 bit wine prefix on a 32 bit wine installation. But in my case, every prefix is 32bit.

This time around, since the WINE variable doesn’t appear to be working, I had to drop it and use the prefix of wine-1.3.32 (static build) with wine-1.3.29 (system install). I installed a few packages using winetricks, after which it suddenly stopped working and started giving this error.

Later on (now) I noticed that some wine processes where still running in background which were causing this problem.

However, the main issue now is, the WINE variable doesn’t appear to be working.

I’m trying to make soundforge 10 work. Currently there analyzer graph is bank.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Fri Nov 11, 2011 6:48 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by Usurp » Fri Nov 11, 2011 8:33 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Fri Nov 11, 2011 9:42 am

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

That is why, if you’re wise, you always run ‘which’ to check check
whether the script/program name you just thought up is going to clash
with anything else. Its also why I said «add them to the right hand
end», as in:

$PATH is searched left to right, so doing it this way guarantees that
pre-existing stuff takes precedence over anything you wrote without
first checking for name clashes.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by perryh » Fri Nov 11, 2011 9:15 pm

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by dE_logics » Sat Nov 12, 2011 7:45 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

I’ve not seen any distro which sets ‘.’ in it’s PATH.

Also why will I need $HOME in $PATH?

PATH for user is —
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin

Also ‘.’ in $HOME doesn’t make sense.

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

That is why, if you’re wise, you always run ‘which’ to check check
whether the script/program name you just thought up is going to clash
with anything else. Its also why I said «add them to the right hand
end», as in:

$PATH is searched left to right, so doing it this way guarantees that
pre-existing stuff takes precedence over anything you wrote without
first checking for name clashes.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Sat Nov 12, 2011 8:55 am

I suggested adding $HOME/bin to your search path, not $HOME.

If you write small shell scripts, e.g. as wrappers for Wine applications
or as a short-hand for common actions and they are intended to only be
used from one login, then a convenient place to keep them is in a
$HOME/bin directory because this keeps clutter out of your login
directory. If you do this you’ll want to include $HOME/bin in the search
path for that login by editing .bash_profile

If such scripts are for more general use they should be put in
«/usr/local/bin» and any associated configuration files should be in
«/usr/local/etc». Make sure that the «/usr/local» structure is backed up
along with «/home».

You should reserve «/bin» and «/usr/bin» for programs and scripts that
are part of your distro. Apart from anything else, if you upgrade your
distro or do a clean install you may loose anything you put in those
directories while, if you backed up the contents of /usr/local then its
easy to drop it back in place after the upgrade or install.

Источник

View previous topic :: View next topic
Author	Message
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Sun Dec 05, 2021 7:07 am    Post subject: [SOLVED]Wine-staging, winetricks and dxvk drive me crazy Hello folks, Sorry for this post title but i am at a point where i really don’t know things work. I did install wine-staging, dxvk and use winetricks. I have to say that I also emerge crossdev to compile Mingw32 for the bot architecture (32,64) and emerged vulkan headers. All my games were running perfectly, nothing to complain about…except i did not understand how everything works so i decided to delete the .wine folder and start again to learn (this learning process is better than playing games!). I don’t even know to start first with wine but let me explain what i have done so far. 1. Emerging wine-staging (current:6.23) 2. Creating the wine prefix but installing a game: Code: wine-staging game.exe . But i also used the wineboot command Code: wineboot-staging -i 3. Trying to run winetricks like this: Code:  WINEPREFIX=/home/username/.wine . And it failed almost at each attempt: Code: Executing mkdir -p /home/username —————————————————— warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug. —————————————————— —————————————————— WINEPREFIX INFO: Drive C: total 28 drwxr-xr-x  7 username username 4096 Dec  5 10:41 . drwxr-xr-x  4 username username 4096 Dec  5 15:16 .. drwxr-xr-x  3 username username 4096 Dec  5 10:41 ProgramData drwxr-xr-x  6 username username 4096 Dec  5 10:41 Program Files drwxr-xr-x  8 username username 4096 Dec  5 10:48 Program Files (x86) drwxr-xr-x  4 username username 4096 Dec  5 10:41 users drwxr-xr-x 20 username username 4096 Dec  5 10:41 windows Registry info: /home/username/.wine/system.reg:#arch=win64 /home/username/.wine/userdef.reg:#arch=win64 /home/username/.wine/user.reg:#arch=win64 —————————————————— —————————————————— warning: wine cmd.exe /c echo ‘%AppData%’ returned empty string, error message «wine: ‘/home/username/.wine’ is a 64-bit installation, it cannot be used with a 32-bit wineserver.» —————————————————— What i don’t understand here is the fact that i don’t user the WINEARCH prefix so it winetricks should handle 32 and 64 wineprefix installation. 4. As winetricks failed, i ran: Code: winecfg-staging and i can add some libraries like quartz, xinput, devenum, d3d11, dxd11, etc. 5. Then tried to install dxvk running this command: Code: WINEPREFIX=/home/username/.wine setup_dxvk-bin.sh install with or without the —symlink flag with the same result: Code: wine: ‘/home/username/.wine’ is a 64-bit installation, it cannot be used with a 32-bit wineserver. Failed to resolve C:windowssystem32. Finally i donwload the dll files thanks to the dxvk git repository and copied them to system32 and syswow64 but the error is different and came from wine: Code: cannot load d3d9.dll but the dll is inside system32 and syswow64 folders. 6. Switched to Windows to play the game while crying. Before i delete the .wine folder, every games were running fast for around almost a year so it means that the problem is me. I don’t understand so i male mistakes. here are some useful information: My emerge —info: Code: Portage 3.0.28 (python 3.9.9-final-0, default/linux/amd64/17.1/desktop, gcc-11.2.0, glibc-2.33-r7, 5.10.76-gentoo-r1 x86_64) ================================================================= System uname: Linux-5.10.76-gentoo-r1-x86_64-Intel-R-_Core-TM-_i7-2600_CPU_@_3.40GHz-with-glibc2.33 KiB Mem:    32865200 total,   1321468 free KiB Swap:     524284 total,    523244 free Timestamp of repository gentoo: Sat, 04 Dec 2021 23:29:52 +0000 Head commit of repository gentoo: 53883750a317f0990e1419ae77e64a2475b7ca51 Timestamp of repository brave-overlay: Fri, 03 Dec 2021 16:36:37 +0000 Head commit of repository brave-overlay: 090fcbe4fb2c59a52eba700bba1fe5913d317113 Timestamp of repository brother-overlay: Mon, 18 Oct 2021 19:36:44 +0000 Head commit of repository brother-overlay: 1a4084241999442052f680a0928d302837f4cf75 Timestamp of repository guru: Thu, 02 Dec 2021 16:51:47 +0000 Head commit of repository guru: 8978a75b0e7f6c76d0fda9455873023aae866239 sh bash 5.1_p8 ld GNU ld (Gentoo 2.37_p1 p0) 2.37 app-shells/bash:          5.1_p8::gentoo dev-java/java-config:     2.3.1::gentoo dev-lang/perl:            5.34.0-r3::gentoo dev-lang/python:          3.8.12_p1::gentoo, 3.9.9::gentoo, 3.10.0_p1::gentoo dev-lang/rust:            1.56.1::gentoo dev-util/cmake:           3.20.5::gentoo sys-apps/baselayout:      2.7-r3::gentoo sys-apps/openrc:          0.44.9::gentoo sys-apps/sandbox:         2.25::gentoo sys-devel/autoconf:       2.13-r1::gentoo, 2.71-r1::gentoo sys-devel/automake:       1.16.4::gentoo sys-devel/binutils:       2.37_p1::gentoo sys-devel/gcc:            11.2.0::gentoo sys-devel/gcc-config:     2.4::gentoo sys-devel/libtool:        2.4.6-r6::gentoo sys-devel/make:           4.3::gentoo sys-kernel/linux-headers: 5.10-r1::gentoo (virtual/os-headers) sys-libs/glibc:           2.33-r7::gentoo Repositories: gentoo     location: /var/db/repos/gentoo     sync-type: git     sync-uri: https://anongit.gentoo.org/git/repo/sync/gentoo.git     priority: -1000     sync-git-verify-commit-signature: yes brave-overlay     location: /var/db/repos/brave-overlay     sync-type: git     sync-uri: https://github.com/gentoo-mirror/brave-overlay.git     masters: gentoo brother-overlay     location: /var/db/repos/brother-overlay     sync-type: git     sync-uri: https://github.com/gentoo-mirror/brother-overlay.git     masters: gentoo guru     location: /var/db/repos/guru     sync-type: git     sync-uri: https://github.com/gentoo-mirror/guru.git     masters: gentoo ACCEPT_KEYWORDS=»amd64″ ACCEPT_LICENSE=»@FREE» CBUILD=»x86_64-pc-linux-gnu» CFLAGS=»-march=native -O2 -pipe» CHOST=»x86_64-pc-linux-gnu» CONFIG_PROTECT=»/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/gnupg/qualified.txt» CONFIG_PROTECT_MASK=»/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php8.1/ext-active/ /etc/php/cgi-php8.1/ext-active/ /etc/php/cli-php8.1/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo» CXXFLAGS=»-march=native -O2 -pipe» DISTDIR=»/var/cache/distfiles» EMERGE_DEFAULT_OPTS=»—alphabetical —backtrack=10 —jobs=9 —keep-going —load-average=9 —verbose-conflicts» ENV_UNSET=»CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR» FCFLAGS=»-march=native -O2 -pipe» FEATURES=»assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr» FFLAGS=»-march=native -O2 -pipe» GENTOO_MIRRORS=»http://distfiles.gentoo.org» LANG=»en_US.utf8″ LDFLAGS=»-Wl,-O1 -Wl,—as-needed» MAKEOPTS=»-j9″ PKGDIR=»/var/cache/binpkgs» PORTAGE_CONFIGROOT=»/» PORTAGE_RSYNC_OPTS=»—recursive —links —safe-links —perms —times —omit-dir-times —compress —force —whole-file —delete —stats —human-readable —timeout=180 —exclude=/distfiles —exclude=/local —exclude=/packages —exclude=/.git» PORTAGE_TMPDIR=»/var/tmp» USE=»X a52 aac acl acpi alsa amd64 bluetooth branding bzip2 cairo cdda cdr cli crypt cups curl dbus dri dts dvd dvdr elogind emboss encode exif flac fortran gdbm gif gpm gtk gui iconv icu ipv6 jpeg lcms libglvnd libnotify libtirpc mad mng mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf png policykit ppds pulseaudio qt5 readline sdl seccomp spell split-usr ssl startup-notification svg tiff truetype udev udisks unicode upower usb vorbis wxwidgets x264 xattr xcb xml xv xvid zlib» ABI_X86=»64″ ADA_TARGET=»gnat_2020″ APACHE2_MODULES=»authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias» CALLIGRA_FEATURES=»karbon sheets words» COLLECTD_PLUGINS=»df interface irq load memory rrdtool swap syslog» CPU_FLAGS_X86=»aes avx mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3″ ELIBC=»glibc» GPSD_PROTOCOLS=»ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx» INPUT_DEVICES=»evdev libinput synaptics» KERNEL=»linux» L10N=»ja fr en» LCD_DEVICES=»bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text» LIBREOFFICE_EXTENSIONS=»presenter-console presenter-minimizer» LUA_SINGLE_TARGET=»lua5-1″ LUA_TARGETS=»lua5-1″ OFFICE_IMPLEMENTATION=»libreoffice» PHP_TARGETS=»php7-3 php7-4″ POSTGRES_TARGETS=»postgres12 postgres13″ PYTHON_SINGLE_TARGET=»python3_9″ PYTHON_TARGETS=»python3_9″ RUBY_TARGETS=»ruby26 ruby30″ SANE_BACKENDS=»net» USERLAND=»GNU» VIDEO_CARDS=»nvidia» XTABLES_ADDONS=»quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account» Unset:  CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS wine version: staging-6.23 wine-mono: 7.0.0 winetricks version: 20210206 sys-devl/crossdev version: 20210621 dev-util/vulkan-headers version: 1.2.189 media-libs/vulkan-loader version: 1.2.189-r1 dxvk-bin version: 1.9.2 I have read tons of informationm, especially on winehq, but nothing changed at all. Please, help me to understand the right way to avoid the Code: wine: ‘/home/username/.wine’ is a 64-bit installation, it cannot be used with a 32-bit wineserver. . If you need more info, please let me know. Thanks in advance, Shiru Last edited by Shiru on Sun Dec 12, 2021 2:09 pm; edited 1 time in total
Back to top
Mistwolf Apprentice Joined: 07 Mar 2007 Posts: 179 Location: Edmonton, AB	Posted: Mon Dec 06, 2021 12:25 am    Post subject: 1) Delete the .wine folder 2) run «WINEARCH=win32 winecfg» 3) install game/run winetricks Multi-lib wine defaults to 64 bit architecture, which has limited support to run things.
Back to top
Chiitoo Administrator Joined: 28 Feb 2010 Posts: 2413 Location: Here and Away Again	Posted: Mon Dec 06, 2021 7:15 pm    Post subject: ><)))°€ The ‘/home/username/.wine’ path is default, so there’s no need to specify ‘WINEPREFIX’ when using it, although it does provide a good chance for confusion later on. :] Regarding the issue with running Winetricks after Wine, do you perhaps have more Wine builds installed than just the one? Perhaps one that’s 32-bit only? This would explain a lot, since you were specifically calling for ‘wine-staging’ in places, but not in others. Try ‘eselect wine list’. _________________ Kind regards, Chiitoo. Sore wa sore, kore wa kore.
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Tue Dec 07, 2021 1:11 pm    Post subject: Mistowolf, Thanks but i need to learn here (it worked for around a year and i need to know why). Chiito, I only have the 6.23 staging version. it’s not clear for to say which build is (32/64): i just checked with eix and i saw Code: ABI_X86=»32 64 In details: Code: Installed versions:  6.23(6.23)^t(10:22:37 AM 12/05/2021)(X alsa cups fontconfig gecko mingw mono mp3 nls opengl perl pulseaudio realtime run-exes sdl ssl staging threads truetype udev udisks unwind usb v4l vkd3d vulkan xcomposite -capi -custom-cflags -dos -gphoto2 -gssapi -gstreamer -kerberos -ldap -netapi -odbc -openal -opencl -osmesa -oss -pcap -pipelight -prelink -samba -scanner -selinux -test -xinerama ABI_MIPS=»-n32 -n64 -o32″ ABI_S390=»-32 -64″ ABI_X86=»32 64 -x32″ ELIBC=»glibc» KERNEL=»-FreeBSD») You are right: no need to use this WINEPREFIX because that’s the default one. I still try everything bu still stuck and i did succeed in the past so there is a solution somewhere…
Back to top
Chiitoo Administrator Joined: 28 Feb 2010 Posts: 2413 Location: Here and Away Again	Posted: Tue Dec 07, 2021 1:49 pm    Post subject: Hmmm, just to be sure, please also post the output from ’emerge —info wine-vanilla wine-staging’ (can omit the actual info part since you already posted that). At this time, I still can’t think of any other reason for a 32-bit only wineserver being used like that, even though the prefix was just created using a build that supports both, 32 and 64. Well, aside from environment variables being set when they shouldn’t. I’ll keep thinking and testing and let you know if I come up with anything else… As a sidey-note, for Winetricks you can also specify the version/flavour using the WINE variable, like so for example: WINE=»wine-staging-6.23″ winetricks dxvk _________________ Kind regards, Chiitoo. Sore wa sore, kore wa kore.
Back to top
Hu Moderator Joined: 06 Mar 2007 Posts: 19775	Posted: Tue Dec 07, 2021 4:57 pm    Post subject: On the subject of environment variables, please provide the output of declare -p | grep WINE, as run from the user shell in which you then run wine.
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Wed Dec 08, 2021 1:52 am    Post subject: Chiito, I don’t hqve wine-vanilla installed. But here’s the wine-staging emerge —info: Code: app-emulation/wine-staging-6.23::gentoo was built with the following: USE=»X alsa -capi cups -custom-cflags -dos fontconfig gecko -gphoto2 -gssapi -gstreamer -kerberos -ldap mingw mono mp3 -netapi nls -odbc -openal -opencl opengl -osmesa -oss -pcap perl -pipelight -prelink pulseaudio realtime run-exes -samba -scanner sdl (-selinux) ssl (staging) -test threads truetype udev udisks unwind usb v4l vkd3d vulkan xcomposite -xinerama» ABI_X86=»32 64 (-x32)» CFLAGS=»-march=native -O2 -pipe -fno-builtin» FEATURES=»news parallel-fetch sandbox merge-sync userpriv usersandbox network-sandbox config-protect-if-modified distlocks preserve-libs userfetch unmerge-logs qa-unresolved-soname-deps binpkg-dostrip strict sfperms unknown-features-warn binpkg-logs usersync protect-owned binpkg-docompress fixlafiles assume-digests ipc-sandbox ebuild-locks pid-sandbox xattr multilib-strict unmerge-orphans» And…I ran the WINE=»wine-staging-6.23″ and despite some errors (if it really was) from output, dxvk was installed and i got 60 and more FPS like before. So it works… So if i use this command i can install dxvk easily? is that was the solution i was searching for? Hu, I ran the command «declare -p | grep WINE» but no output at all. I don’t know if that is a good thing or not… Shiru
Back to top
Chiitoo Administrator Joined: 28 Feb 2010 Posts: 2413 Location: Here and Away Again	Posted: Wed Dec 08, 2021 12:49 pm    Post subject: Shiru wrote: I don’t hqve wine-vanilla installed. Right, I wanted you to try the command as I wrote it just so we can be as sure about it as you. :] Quote: But here’s the wine-staging emerge —info: Code: app-emulation/wine-staging-6.23::gentoo was built with the following: USE=»X alsa -capi cups -custom-cflags -dos fontconfig gecko -gphoto2 -gssapi -gstreamer -kerberos -ldap mingw mono mp3 -netapi nls -odbc -openal -opencl opengl -osmesa -oss -pcap perl -pipelight -prelink pulseaudio realtime run-exes -samba -scanner sdl (-selinux) ssl (staging) -test threads truetype udev udisks unwind usb v4l vkd3d vulkan xcomposite -xinerama» ABI_X86=»32 64 (-x32)» CFLAGS=»-march=native -O2 -pipe -fno-builtin» FEATURES=»news parallel-fetch sandbox merge-sync userpriv usersandbox network-sandbox config-protect-if-modified distlocks preserve-libs userfetch unmerge-logs qa-unresolved-soname-deps binpkg-dostrip strict sfperms unknown-features-warn binpkg-logs usersync protect-owned binpkg-docompress fixlafiles assume-digests ipc-sandbox ebuild-locks pid-sandbox xattr multilib-strict unmerge-orphans» And…I ran the WINE=»wine-staging-6.23″ and despite some errors (if it really was) from output, dxvk was installed and i got 60 and more FPS like before. So it works… So if i use this command i can install dxvk easily? is that was the solution i was searching for? Hu, I ran the command «declare -p | grep WINE» but no output at all. I don’t know if that is a good thing or not… Very strange. That specifying the Wine version via the WINE variable for Winetricks makes it work further suggests some other version is being used otherwise, and there doesn’t seem to be any variables set either… That is how I usually install the latest ‘dxvk’, but no, you normally don’t need to use the WINE variable like that. It only makes sense when there are more than one Wine build to choose from. By the way, regarding running Winetricks, I don’t actually see it in the earlier posts, so were you running it on the CLI completely, or actually using the GUI (the GUI is not maintained too much, so there most likely are issues lurking). Did you ever build and/or install Wine manually in the past? What do you get when you run a plain ‘wine —version’? _________________ Kind regards, Chiitoo. Sore wa sore, kore wa kore.
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Thu Dec 09, 2021 10:26 pm    Post subject: Hello Chiito, Thanks for your time and your replies. In fact, as for Winetricks, i am using both (GUI/CL) but in major cases it’s the GUi. As you said, i have to focus on CL in order to avoid more issues. I didn’t build manually Wine: only emerged it with Portage. So, is that means that i mess up with some USE flags or packages related to Wine? Shiru
Back to top
Chiitoo Administrator Joined: 28 Feb 2010 Posts: 2413 Location: Here and Away Again	Posted: Fri Dec 10, 2021 11:20 am    Post subject: Shiru wrote: So, is that means that i mess up with some USE flags or packages related to Wine? No, I don’t think there are any such flags that would cause this. Did you try the last suggestion from my previous post? What is the output of ‘wine —version’ when you run it exactly like this? _________________ Kind regards, Chiitoo. Sore wa sore, kore wa kore.
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Sat Dec 11, 2021 2:05 pm    Post subject: Hello Chiito, The Code: wine —version command returns Code: wine-5.0.1 . Is this helps? Shiru Last edited by Shiru on Sun Dec 12, 2021 1:33 am; edited 1 time in total
Back to top
Chiitoo Administrator Joined: 28 Feb 2010 Posts: 2413 Location: Here and Away Again	Posted: Sat Dec 11, 2021 2:31 pm    Post subject: Indeed it does! This means that, in one way or the other, you do indeed have another version of Wine installed. Did you try the command ‘eselect wine list’ from earlier? If that only returns one version, and ’emerge —info wine-vanilla’ returns nothing, then perhaps try the following: Code: $ which wine # This should probably return: /usr/bin/wine $ ls -l /usr/bin/wine # This will probably return something like: /usr/bin/wine -> /usr/bin/wine-vanilla-5.0.1 _________________ Kind regards, Chiitoo. Sore wa sore, kore wa kore.
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Sun Dec 12, 2021 1:32 am    Post subject: You were right!! Code: which wine returned Code: /usr/local/bin//wine By the way, i checked the version and it was the Code: wine-5.0.1 And Code: ls -l /usr/bin/wine returned Code:  /usr/bin/wine -> /usr/bin/wine-staging-6.23 So the question is: where the wine-5.0.1 came from?
Back to top
Hu Moderator Joined: 06 Mar 2007 Posts: 19775	Posted: Sun Dec 12, 2021 2:35 am    Post subject: If it is in /usr/local, then you installed it there. When was it last modified?
Back to top
Shiru n00b Joined: 20 Oct 2014 Posts: 59	Posted: Sun Dec 12, 2021 5:15 am    Post subject: I cannot deny that i installed it here but i just cannot remember doing it (scary…) This version has been installed in March 21st. EDIT: i delete the /usr/local/bin/wine* and i don’t have any issue at all now. Thanks Hu and ChIIto for your help. I marked this thread as solved.
Back to top
Display posts from previous:

You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

---

---

---

---

---

---

---

---

---

Страницы: [1]   Вверх

I’m new to linux and I’m trying to install wine so I can play Hearthstone.
I following this tutorial: https://linuxconfig.org/how-to-install-battle-net-on-ubuntu-22-04-linux-desktop

I run winetricks and everything is OK until Step 3. Then, I get some errors that even if I press OK, they keep reappering and nothing else happens — until I stop the terminal.

Below you can see both images that show up (somewhere between Step 3 and 4)

image1

image2

And here a paste of the terminal while the errors are happening:

guin0x@guin0x-server:~$ winetricks
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20210206 - sha256sum: 0f21da98811e0bfda16a7d6d6b8e860a9cedbd4e836c7dd9b02f068d3092ee2e with wine-6.0.3 (Ubuntu 6.0.3~repack-1) and WINEARCH=win64
winetricks GUI enabled, using zenity 3.42.1
Executing w_do_call corefonts
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_corefonts 
Executing w_do_call andale
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_andale 
Executing cabextract -q -d /home/guin0x/.wine/dosdevices/c:/windows/temp /home/guin0x/.cache/winetricks/corefonts/andale32.exe
------------------------------------------------------
warning: Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/guin0x/.wine terminate
------------------------------------------------------
Executing wine regedit C:windowsTemp_register-font.reg
Executing wine64 regedit C:windowsTemp_register-font.reg
0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
Executing cp /home/guin0x/.wine/dosdevices/c:/windows/temp/_register-font.reg /tmp/winetricks.WeeZhyWc/_reg_90ad6a9f_10400.reg
Executing wine regedit C:windowsTemp_register-font.reg
Executing wine64 regedit C:windowsTemp_register-font.reg
0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
Executing cp /home/guin0x/.wine/dosdevices/c:/windows/temp/_register-font.reg /tmp/winetricks.WeeZhyWc/_reg_f6204652_10400.reg
Executing w_do_call arial
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.

Thanks a lot in advance!

---