Wine stuck in shell after crashing once | Debian

[Alvenster]

In order to see to what extend wine could run programs, I tried running Dolphin 5.0 ( I know there is a Linux build ).
Wine version : 7.0 Linux distro : Debian 11

Installation goes perfectly, after that I can run Dolphin, configure controllers, etc with no problem at all.

I configured Dolphin to use Direct 3D then I launched the ROM ( Metroid Prime 2 : Echoes )

Without too much suprise, the windows crashes, and I'm forced to kill the Wine process manually ( I tried using Ctrl+C, Ctrl-Z, and using wineserver -k)

This is where things start to get messy. After crashing, Wine is not able to run programs that normally run smoothly. It just stays in the shell without doing anything and just printing some "fixme" errors.

If I want to make it work, I've got to restart my session...

Is there something I am missing? I am quite new to Linux. It feels like killing processes the way I did is wrong... How should I do that?

Btw I mentionned Dolphin but it is the same with every other program when they crash.

Thanks a lot. Tell me if you need more information

[jkfloris]

It just stays in the shell without doing anything and just printing some "fixme" errors.

Can you post a terminal output?

[Alvenster]

This is the terminal output when the process goes perfectly:

Code: Select all

$wine Dolphin.exe
0108:fixme:heap:RtlSetHeapInformation 0000000007E80000 0 000000000011F6E0 4 stub
0108:fixme:heap:RtlSetHeapInformation 0000000007FC0000 0 000000000011F6E0 4 stub
0108:fixme:heap:RtlSetHeapInformation 00000000080D0000 0 000000000011F6E0 4 stub
0108:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0108:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0108:fixme:imm:ImeSetActiveContext (0x1aef5940, 1): stub
0108:fixme:imm:ImmReleaseContext (000000000001007C, 000000001AEF5940): stub
0080:fixme:imm:ImeSetActiveContext (0x3ce80, 0): stub
0080:fixme:imm:ImmReleaseContext (0000000000010020, 000000000003CE80): stub

Dolphin window opens right after


And this is the terminal when I try to restart Dolphin after it had crashed once :

Code: Select all

0144:fixme:heap:RtlSetHeapInformation 0000000007E80000 0 000000000011F6E0 4 stub
0144:fixme:heap:RtlSetHeapInformation 0000000007FC0000 0 000000000011F6E0 4 stub
0144:fixme:heap:RtlSetHeapInformation 00000000080D0000 0 000000000011F6E0 4 stub
0144:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0144:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0144:fixme:imm:ImeSetActiveContext (0x1aef50d0, 1): stub
0144:fixme:imm:ImmReleaseContext (0000000000020046, 000000001AEF50D0): stub

No window open after the shell displayed these lines.

Thanks for helping me btw

[jkfloris]

Unfortunately, there is not much information in the terminal output.

I configured Dolphin to use Direct 3D

Do you have the same problems when using Vulkan or OpenGL?

I have the feeling that Wine remains running after the crash.
Does "pgrep -a wine" show something?

Common questions:
- What is the exact version of Dolphin (e.g. 5.0-15940)
- Have you installed other programs in Wine/ used some winetricks?
- What graphics card + driver do you have?

[Alvenster]

I tried pgrep -a wine and I got this in the standard output :

Code: Select all

10700 /opt/wine-stable/bin/wineserver
10709 C:\windows\system32\winedevice.exe                                                                  
10717 C:\windows\system32\winedevice.exe                                                                  
10799 winedbg --auto 256 420  

I tried to kill them one by one at first using

Code: Select all

kill PID

but the some of the processes were not responding so I had to kill them using

Code: Select all

kill -9 PID

.
I didn't work though...


The common questions:

Graphic card : Mesa Intel® UHD Graphics 600 (GLK 2)
I installed and tried to run both Dolphin 5.0 and Dolphin 3.0 stable versions after I saw it was running perfectly on wine in the database.
I definitely knew that DirectX was causing the problem because the emulation window wouldn't even open, so my dolphins are configured on OpenGL( Vulkan does show on the menu ). The ROM ran once and then I couldn't make it work again. The emulation window still open though but doesn't run anything except showing "Clearing Code Cache" as a title and not wanting to close without brute forcing it.

HOWEVER I TRIED SOMETHING!!! (proud of myself as a beginner)
Indeed i tried to run the wine Dolphin.exe as root and I got a completely different output with plenty of errors:

Code: Select all

0084:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0084:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0084:err:systray:initialize_systray Could not create tray window
0100:fixme:heap:RtlSetHeapInformation 0000000007E80000 0 000000000011F6E0 4 stub
0108:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0108:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0108:err:systray:initialize_systray Could not create tray window
0100:fixme:heap:RtlSetHeapInformation 0000000007FC0000 0 000000000011F6E0 4 stub
0100:fixme:heap:RtlSetHeapInformation 00000000080D0000 0 000000000011F6E0 4 stub
0100:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0100:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0100:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0100:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
^C0118:fixme:console:default_ctrl_handler Terminating process fc on event 0

I had to use ctrl+C because at some point the entire system froze (even my music stopped) and while I was writing on paper all this precious output it unfroze but everything was lagging and the shell was printing the same error message in repeat.

However this "Application tried to create a window, but no driver could be loaded." and " Make sure that your X server is running and that $DISPLAY is set correctly." ringed a bell so looked for it and found this on stackoverflow https://stackoverflow.com/questions/525 ... -correctly.
I tried to set the $DISPLAY to 0 but it didn't work and printed a similar output. Im posting it in case if you need it:

Code: Select all

0084:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0084:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0084:err:systray:initialize_systray Could not create tray window
0100:fixme:heap:RtlSetHeapInformation 0000000007E80000 0 000000000011F6E0 4 stub
No protocol specified
0108:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0108:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0108:err:systray:initialize_systray Could not create tray window
0100:fixme:heap:RtlSetHeapInformation 0000000007FC0000 0 000000000011F6E0 4 stub
0100:fixme:heap:RtlSetHeapInformation 00000000080D0000 0 000000000011F6E0 4 stub
0100:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0100:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0100:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0100:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.

I then tried installing Xvfb. It was indeed not installed. I installed it. But it didn't work and I got the same errors again.
I rebooted my computer just to make sure. And now Dolphin doesn't even run anymore, not even once. I was in root though. So I tried running it as "normal user", and it worked! Still have this "Clearing code cache " crashing issue just like at the very beginning. I went through the pgrep -a wine process and killed all processes after brute forcing dolphin. Tried to relaunch Dolphin again and it didn't work. I was curious to see if pgrep -a wine was going to print me the same remaining processes and it was the same except that the process "3275 winedbg --auto 256 416 " wasn't running anymore.

I'm so confused right now.

I am a beginner at Linux and I saw many warnings about running Wine as root so maybe this whole root thingy wasn't necessary. When I was trying to get you the exact versions of Dolphin I was using, I realized that I downloaded stable versions instead of the highly advised beta versions. So I uninstalled the stable version to try and run Dolphin 5.0-15445. And now everything works perfectly. Vulkan and DirectX 11 and 12 show up. But when I use DirectX Dolphin crashes. But I can relaunch it again without any problem!

So there is definitely a problem with Dolphin stable versions. And I think that Wine developers should take a look at these remaining processes after a crash and I hope these terminal outputs can help them solving this problem.


Anyway, I am able to run Dolphin the way I wanted with Vulkan and if I dig it a bit more I might find a way to use it with DirectX.

A HUGE THANK YOU FOR YOUR TIME. Any advice on how to correctly use Linux for beginners are welcome

[ssmithterrry]

Maybe the problem is simply that you do not have a very powerful computer. If you are using an Intel UHD Graphics 600 graphics card, then you probably have an Intel Celeron processor. Of course I could be wrong