https://bugs.winehq.org/show_bug.cgi?id=39882
Bug ID: 39882 Summary: Severe graphics glitch in Sibelius 6 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: sebastianhatt@gmail.com Distribution: ---
Created attachment 53250 --> https://bugs.winehq.org/attachment.cgi?id=53250 Screenshot 1
Every time Sibelius starts (version 6 as well as 6.2), some areas on the screen are "frozen" making it virtually impossible to use the program, especially the drop down menus (see the attached screenshot 1). The areas are still frozen, when I switch to other programs or minimize Sibelius, so it affects the whole system (see screenshot 2). They go away again, when Sibelius is closed.
Some of the areas keep showing the same image, others blend what is currently behind them together with with what was previously there, leaving a trail eg. when I move a window around. None of the areas prevent me from clicking whatever they are obscuring, although obviously it is not possible to see, what I'm clicking on.
The areas appear in exactly the same spot every time the program is run. Their location is absolute and is unaffected by moving the main window or anything else. However, they change position the first time the score is played back/stopped.
The log shows four calls to LockWindowUpdate, two using the same handle, two using nil. These calls may or may not be related to the frozen/locked areas on the screen.
From the log:
fixme:win:LockWindowUpdate (0x20632), partial stub!
and
fixme:win:LockWindowUpdate ((nil)), partial stub!
https://bugs.winehq.org/show_bug.cgi?id=39882
--- Comment #1 from sebastianhatt@gmail.com --- Created attachment 53251 --> https://bugs.winehq.org/attachment.cgi?id=53251 Screenshot 2
https://bugs.winehq.org/show_bug.cgi?id=39882
--- Comment #2 from sebastianhatt@gmail.com --- Created attachment 53252 --> https://bugs.winehq.org/attachment.cgi?id=53252 log
https://bugs.winehq.org/show_bug.cgi?id=39882
--- Comment #3 from sebastianhatt@gmail.com --- Comment on attachment 53251 --> https://bugs.winehq.org/attachment.cgi?id=53251 Screenshot 2
The areas changed position when I played the score in Sibelius. They remained at this new position after and switching to LibreOffice.
https://bugs.winehq.org/show_bug.cgi?id=39882
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #4 from Nikolay Sivov bunglehead@gmail.com --- What is your wine version?
https://bugs.winehq.org/show_bug.cgi?id=39882
sebastianhatt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.8
https://bugs.winehq.org/show_bug.cgi?id=39882
--- Comment #5 from sebastianhatt@gmail.com --- Sorry, I forgot to select the version. I use WINE 1.8. I got the same result with WINE 1.7.22. I'm using PlayOnLinux as a frontend, but I don't suppose that should make much of a difference.
https://bugs.winehq.org/show_bug.cgi?id=39882
sebastianhatt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major
--- Comment #6 from sebastianhatt@gmail.com --- UPDATE: -the latest winehq-devel 1.9.0 also has the bug (this time I carefully followed the instructions on http://wiki.winehq.org/Bugs, installed the latest development version of wine (without PlayOnLinux), made a clean wine prefix, reinstalled Sibelius. Same result. -wine 1.4, wine 1.5 and wine 1.5.10 do NOT have the bug. -wine 1.5.11 and wine 1.5.12 do NOT have the bug, but have other problems specific to those versions -wine 1.5.13 introduces the bug!
For now I will stick to 1.5.10. However, Sibelius 6 runs much slower on older wine versions than on 1.9.0 and other recent versions.
Wine 1.5.13 changelist lists among others the following changes: - Client-side window rendering using the DIB engine. - Support for transparent window areas using color keying. (https://www.winehq.org/announce/1.5.13) Specifically, Alexandre Julliard has made lost of changes to user32 and gdi32 (graphics/window handling) that are possible culprits.
Both could have something to do with this bug.
What do I do from here? I'm a wine newb. Do I have to use git bisect? It looks complicated. Any help?
https://bugs.winehq.org/show_bug.cgi?id=39882
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
https://bugs.winehq.org/show_bug.cgi?id=39882
sebastianhatt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.8 |1.5.13
--- Comment #7 from sebastianhatt@gmail.com --- UPDATE: I installed 32-bit Xubuntu inside VirtualBox and installed the latest development version of wine on it (compiled from git). There was no sign of the bug. However, it is present when running the same version of wine on my host OS, Linux Mint (64-bit, MATE edition). This could indicate that it's a problem with my setup. To find out if it's a driver issue, I tested it with both the nouveau and the nvidia driver, and the result was the same. So perhaps it's a problem with the MATE?
I tried to bisect the bug, but I have trouble compiling wine on 64-bit Mint. That's why I installed 32-bit Xubuntu on a virtual machine, to allow me to compile wine and use bisect.
BTW. I've found that Sibelius runs too slowly in 1.5.10 for any serious work. So my solution for now is to run Sibelius on a virtual Windows machine :/
https://bugs.winehq.org/show_bug.cgi?id=39882
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #8 from winetest@luukku.com --- You could try wine 1.9.21 or wine-staging 1.9.21 and see if the bug is still valid.
https://bugs.winehq.org/show_bug.cgi?id=39882
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #9 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.18?