https://bugs.winehq.org/show_bug.cgi?id=56877
Bug ID: 56877 Summary: mozaBook: CEF black box instead of content Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: balint.mate@mozaweb.com Distribution: ---
Created attachment 76683 --> https://bugs.winehq.org/attachment.cgi?id=76683 sample video and log
- mozaBook is an educational presentation software developed by us (Mozaik Education) which uses our custom windowing library based on Windows GDI+.
- We use CEF in several windows for example Number line (which is an HTML application). Sample in the video. - If I move the mouse pointer across the header the CEF content becames black however if I move out the pointer from the side or the bottom it's becoming black only if I click outside of the CEF window. - The CEF content only comes back when I click inside of the window in such a way that it needs to repaint (refresh) itself. - It does not work in any version of the mozaBook (64 bit version).
Wine version: wine-9.11 (Staging)
Possibly solution tried (unsuccessful): - --no-sandbox - --disable-gpu - --disable-gpu-compositing - Setting the WINEDLLOVERRIDES=libglesv2=d environment variable. - --use-views - --off-screen-rendering-enabled - Disallowing the window manager to decorate and control the windows. - Emulating a virtual desktop.
Microsoft corefonts and gdiplus were installed with the winetricks program.
The software can be freely downloaded and tested. Download URL: https://download.us.mozaweb.com/mozabook/mozaBook64_v2024.2.105_Setup_MIN.ex...
https://bugs.winehq.org/show_bug.cgi?id=56877
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Using wine-staging-9.8, I ran "winetricks corefonts gdiplus" and then installed the program. Apparently another order breaks it, at least it did for me. I got a lot of crashes during startup, might or might not be random.
As someone who has no idea about your application, can you give simple instructions on how to reproduce the problem?
https://bugs.winehq.org/show_bug.cgi?id=56877
Bálint Máté balint.mate@mozaweb.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #2 from Bálint Máté balint.mate@mozaweb.com --- Created attachment 76714 --> https://bugs.winehq.org/attachment.cgi?id=76714 mozaBook instructions
Sample video on how to reproduce the CEF black screen bug.
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #3 from Bálint Máté balint.mate@mozaweb.com --- (In reply to Fabian Maurer from comment #1)
Using wine-staging-9.8, I ran "winetricks corefonts gdiplus" and then installed the program. Apparently another order breaks it, at least it did for me. I got a lot of crashes during startup, might or might not be random.
As someone who has no idea about your application, can you give simple instructions on how to reproduce the problem?
Dear Fabian Maurer!
The crashes during the startup could be caused because of the missing ntlm_auth. This can be solved by installing the winbind package (on Debian at least).
I have attached a simple video tutorial on how to reproduce the bug. The video starts after you logged in.
To use the software as a demo user, you need to registrate at https://www.mozaweb.com/en/signup This step is completely free and does not require any credit card information.
After you registrated, you need to click on the Demo button in mozaBook and login with your account. The demo version starts a 30 day free trial.
Since the last test we realised that pointer cursor change can affect when the CEF content goes black. I'm using:
- Operating System: Debian GNU/Linux 12 - KDE Plasma Version: 5.27.5 - KDE Frameworks Version: 5.103.0 - Qt Version: 5.15.8 - Kernel Version: 6.1.0-21-amd64 (64-bit) - Graphics Platform: X11 - Processors: 12 × 11th Gen Intel® Core™ i5-11400 @ 2.60GHz - Memory: 15.4 GiB of RAM - Graphics Processor: Mesa Intel® Graphics
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- I made an account on 28.6.2024, and it tells me my 30 day trial has expired (05.06.2023-05.07.2023)
Not sure what went wrong, I have never had an account before. Maybe the trial is bound to some computer info that is the same on all Wine instances? Anyways, I can't test since I only got limited mode to work with.
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #5 from Bálint Máté balint.mate@mozaweb.com --- (In reply to Fabian Maurer from comment #4)
I made an account on 28.6.2024, and it tells me my 30 day trial has expired (05.06.2023-05.07.2023)
Not sure what went wrong, I have never had an account before. Maybe the trial is bound to some computer info that is the same on all Wine instances? Anyways, I can't test since I only got limited mode to work with.
It seems like all Wine instances has the same OS Serial (1124073472) which caused the trial not to work. Will work on that, thank you for your observation.
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #6 from Fabian Maurer dark.shadow4@web.de --- Yeah, maybe the HDD serial info is the same on all wine instances. For me "wine wmic diskdrive get model,serialNumber" gives
Wine Disk Drive WINEHDISK
I'm pretty sure Wine doesn't have any serials for drives.
Regarding the actual issue, I didn't get to it yet, I hope I can take a look soon.
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #7 from Hans Leidekker hans@meelstraat.net --- (In reply to Fabian Maurer from comment #6)
Yeah, maybe the HDD serial info is the same on all wine instances. For me "wine wmic diskdrive get model,serialNumber" gives
Wine Disk Drive WINEHDISK
I'm pretty sure Wine doesn't have any serials for drives.
We do return drive serial numbers (via dbus) but not every drive supports it.
https://bugs.winehq.org/show_bug.cgi?id=56877
--- Comment #8 from Fabian Maurer dark.shadow4@web.de ---
We do return drive serial numbers (via dbus) but not every drive supports it.
Ah, alright. It didn't work because of my sandboxing that blocked dbus access. I didn't expect dbus to be an extra loop so I missed it, thanks for the explanation.
https://bugs.winehq.org/show_bug.cgi?id=56877
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- I had some crashes when clicking "Number Line", but after I made sure users/fabian/Desktop exists, it works now. I can reproduce the issue.
-
WineHQ Bugzilla