box64 icon indicating copy to clipboard operation
box64 copied to clipboard

Black squares on window in VaraHF

Open Beiri22 opened this issue 7 months ago • 12 comments

Hi,

i am using an Orange Pi Zero 2W with OrangeOS (based on arch). I am using the latest VaraHF via Wine from aur package wine-tkg-staging-wow64-bin.

With the aur packge box64 0.3.4-2 it worked ok (but i could not use winetricks due to an error); so i switched to box-git (installed 30min ago). With that winetricks is working well, but I get black areas on my window. See attachment.

As the version change of box64 made this happen, I chose to put the issue here. Any idea?

Image

Beiri22 avatar May 20 '25 15:05 Beiri22

(for reference, it is supposed to look more like that:)

Image

Beiri22 avatar May 20 '25 15:05 Beiri22

You mean with box64 v0.3.4 it was working fine?

ptitSeb avatar May 20 '25 15:05 ptitSeb

I did some experiments with -0.3.4. and -git.

When using a fresh wine prefix and starting the application the first time, it's looking ok. When I close Vara and start it again, the black areas are there. And it´his seems to be with both box versions. So maybe the problem lies somewhere else.

On my desktop its running ok. I will try wine-tkg-staging-wow64-bin there without box64.

Beiri22 avatar May 20 '25 15:05 Beiri22

So it appears only on 2nd run?

ptitSeb avatar May 20 '25 15:05 ptitSeb

on 2nd and all following

Beiri22 avatar May 20 '25 15:05 Beiri22

1.) Using the same version of wine on my desktop w/o box64 shows no problem at all. 2.) On the first start of Vara with box64 (Main window looks ok), one of the settings windows is also blackened.

Beiri22 avatar May 20 '25 15:05 Beiri22

I did some more experiments: 1.) Sometimes its working for a few restarts of the program before finally blackening out. I cannot surely say, what "condition" changes... 2.) When it works, you see all the blocks black for a split second, and then showing the actual components 3.) When it does not work any more, the mouse symbol is not visible in the window and it seems I cannot click anything. 4.) In any case the settings window is mostly black. 5.) It seems that when it's not working, the following part is not logged:

0024:fixme:pdh:PdhVbAddCounter 09E3BF18, "\\                                                                                                                                                                                                                                                                   (0)\\% Processor Time", 0020F964: stub!
0024:fixme:pdh:PdhVbAddCounter 09E3BF18, "\\                                                                                                                                                                                                                                                                   (1)\\% Processor Time", 0020F964: stub!
0024:fixme:pdh:PdhVbAddCounter 09E3BF18, "\\                                                                                                                                                                                                                                                                   (2)\\% Processor Time", 0020F964: stub!
0024:fixme:pdh:PdhVbAddCounter 09E3BF18, "\\                                                                                                                                                                                                                                                                   (3)\\% Processor Time", 0020F964: stub!

6.) The program changes the audio device in its ini file. Maybe this is related. I may do some experiments soon.

Beiri22 avatar May 20 '25 21:05 Beiri22

When the ini references a real audio device, it's all black like in my first screenshot. If it references a fake audio device name, only the bottom box is black. In all cases the audio settings dialog is black and not functional.

When I disable audio by setting sound=pulse with winetricks and BOX64_NOPULSE=1 then even the settings dialog is shown properly. So this definitely related to audio devices.

Beiri22 avatar May 20 '25 22:05 Beiri22

does this give you any clue?

Beiri22 avatar May 22 '25 20:05 Beiri22

No. But I don't know VaraHF very well.

What I'm wondering is: is it a regression on box64 side or is it a newer version of VaraHF that broken it?

ptitSeb avatar May 22 '25 21:05 ptitSeb

I'm new to both. But i saw the Last commits of @AndreRH citing vara as example and regarding wow64. As I am using a wow64 build of wine, may he might have an idea?

Beiri22 avatar May 23 '25 03:05 Beiri22

I mentioned it in the context of a dll build of box64, which is supposed to be used in a arm64 build of wine. Note that this is the opposite of what you are doing (running x86_64 wine in box64). Though if you just want it to run, you can try https://github.com/AndreRH/hangover which has pre build packages for what I mentioned. I think I might have exchanged some msvcrt component of the vara installation to make it run though...

AndreRH avatar May 24 '25 08:05 AndreRH