[Bug 44574] New: Wine 3.1 - Office 2013 starts with a black screen!
https://bugs.winehq.org/show_bug.cgi?id=44574
Bug ID: 44574
Summary: Wine 3.1 - Office 2013 starts with a black screen!
Product: Wine
Version: 3.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eduardolucioac(a)gmail.com
Distribution: ---
Created attachment 60544
--> https://bugs.winehq.org/attachment.cgi?id=60544
Office 2013 starts with a black screen
> =====================
* PROBLEM:
Office 2013 starts with a black screen!
https://i.stack.imgur.com/PKLGo.jpg
NOTE: See image ("Office 2013 starts with a black screen" attachment)!
> =====================
* INSTALLATION SCHEME USED:
WINEARCH=win32 WINEPREFIX=~/office2013 wine wineboot
WINEARCH=win32 WINEPREFIX=~/office2013 wine '<PATH_TO_SETUP_EXE>/setup.exe'
WINEARCH=win32 WINEPREFIX=~/office2013 wine 'C:\Program Files\Microsoft
Office\Office15\WINWORD.EXE'
> =====================
* THESE INTERVENTIONS DID NOT WORK:
cat << EOF > "Direct3D.reg"
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"MaxVersionGL"=dword:00030002
EOF
WINEARCH=win32 WINEPREFIX=~/.PlayOnLinux/wineprefix/office2013 wine regedit
"Direct3D.reg"
rm -f "Direct3D.reg"
WINEARCH=win32 WINEPREFIX=~/.PlayOnLinux/wineprefix/office2013 winetricks -q
corefonts
WINEARCH=win32 WINEPREFIX=~/.PlayOnLinux/wineprefix/office2013 winetricks -q
msxml6
WINEARCH=win32 WINEPREFIX=~/.PlayOnLinux/wineprefix/office2013 winetricks -q
riched20
NOTE I: "wbind" installed.
NOTE II: 3.1 is the wine version.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 --- Comment #1 from Eduardo Lúcio Amorim Costa <eduardolucioac(a)gmail.com> --- Created attachment 60545 --> https://bugs.winehq.org/attachment.cgi?id=60545 The output from the terminal! The output from the terminal attached! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 --- Comment #2 from Eduardo Lúcio Amorim Costa <eduardolucioac(a)gmail.com> --- SOLVED! For some reason when I changed the version of wine (see image) in PlayOnLinux the Office 2013 stopped working even though I reinstall it in the same version that was working earlier. I think this may be a bug in Wine or PlayOnLinux. The solution was remove the wine, wine-mono, wine_gecko, winetricks, and playonlinux, restart the OS and reinstall everything again. Thanks! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #3 from Fabian Maurer <dark.shadow4(a)web.de> --- So you can't reproduce the bug anymore? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 --- Comment #4 from Eduardo Lúcio Amorim Costa <eduardolucioac(a)gmail.com> --- Yes! Install the app and changed the version of wine (ex.: 3.0 -> 3.2) in PlayOnLinux. Thanks! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Fabian Maurer <dark.shadow4(a)web.de> --- Resolving WORKSFORME then. If the issue reappears, just reopen. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Vlad <375333400829(a)ya.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |375333400829(a)ya.ru --- Comment #6 from Vlad <375333400829(a)ya.ru> --- i see this bug in wine 3.4 How fix? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|-unknown |d2d Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #7 from Nikolay Sivov <bunglehead(a)gmail.com> --- It tries to use newer Direct2D API that we don't implement. To workaround you should set DWORD value named "max_version_factory" to 0 at: --- HKCU/Software/Wine/Direct2D/ --- -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Ali <a.shahbazi91(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.shahbazi91(a)gmail.com --- Comment #8 from Ali <a.shahbazi91(a)gmail.com> --- (In reply to Nikolay Sivov from comment #7)
It tries to use newer Direct2D API that we don't implement. To workaround you should set DWORD value named "max_version_factory" to 0 at:
--- HKCU/Software/Wine/Direct2D/ ---
Setting the 'max_version_factory' value to 0 fixes the black screen issue but the whole OS hangs right after showing the new document dialog. Following is the terminal output with "WINEDEBUG=+tid,+timestamp,+seh" set. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 --- Comment #9 from Ali <a.shahbazi91(a)gmail.com> --- Created attachment 60844 --> https://bugs.winehq.org/attachment.cgi?id=60844 wine 3.4 terminal output -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 taisfmq(a)live.cn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |taisfmq(a)live.cn --- Comment #10 from taisfmq(a)live.cn ---
Setting the 'max_version_factory' value to 0 fixes the black screen issue but the whole OS hangs right after showing the new document dialog.
Confirmed in Wine 3.4 Fedora 27 inside docker. After clicking "Open File" it hangs with logs: wine: Unhandled page fault on read access to 0x000000cc at address 0xXXXXXXXX (thread 0009), starting debugger... Can't attach to process 0008: error 5 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 zappacor(a)hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zappacor(a)hotmail.com --- Comment #11 from zappacor(a)hotmail.com --- (In reply to Nikolay Sivov from comment #7)
It tries to use newer Direct2D API that we don't implement. To workaround you should set DWORD value named "max_version_factory" to 0 at:
--- HKCU/Software/Wine/Direct2D/ ---
I used this as a workaround but what really solved it was to just install uninstall wine 3.0 and reinstall it again (I'm relying on playonlinux for that) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 --- Comment #12 from Nikolay Sivov <bunglehead(a)gmail.com> --- Please retest with current Wine or 3.19 when it's out, without any registry tweaks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Summary|Wine 3.1 - Office 2013 |Microsoft Office 2013 |starts with a black screen! |client area is rendered | |black (Direct2D) Status|REOPENED |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |0ab71185034a065d1e6161b7226 | |292c2e4ef4c70 --- Comment #13 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, with Wine 3.19 release, the client area started to render properly hence I assume Nikolay in comment #12 was already referring to the following commits that ought to fix this. --- snip --- $ git log --pretty=format:"%h %an %ad%n%s%n" wine-3.18...wine-3.19 -- dlls/d2d1 926d98ef857 Nikolay Sivov Thu Oct 25 16:36:50 2018 +0300 d2d1: Add ID2D1Factory2 stub. 7ef66068f21 Nikolay Sivov Tue Oct 23 12:18:42 2018 +0330 d2d1: Implement d2d_device_context_ID2D1DeviceContext_DrawGlyphRun(). 0ab71185034 Nikolay Sivov Thu Oct 18 16:19:28 2018 +0300 d2d1: Return S_OK from d2d_effect_SetValue(). 48bcae100ee Nikolay Sivov Thu Oct 18 16:19:27 2018 +0300 d2d1: Return S_OK from RegisterEffectFromString(). e55aca8f498 Daniel Ansorregui Mon Oct 15 20:17:15 2018 +0100 d2d1: Use default NULL argument in SetBlendState call. --- snip --- Unfortunately none of the commits mention a specific bug so I had to waste a bit of time to check on their impact each. With Wine 3.18 the whole client area was rendered black and the console was spammed with following relevant console FIXMEs: --- snip --- 0061:fixme:d2d:d2d_factory_RegisterEffectFromString iface 0x6375f068, effect_id {f82ea997-8fa9-490a-8493-5bc0b3a640b7}, property_xml L"<?xml version='1.0'?><Effect> <Property name='DisplayName' type='string' value='AirSpace Blend Effect'/> <Property name='Author' type='string' value='Microsoft Corporation'/> <Property name='Category' type='string' value='Internal'/> <Property name='Description' type='string' value='AirSpace blend ef"..., bindings 0x2c6ac98, binding_count 1, effect_factory 0x28e05af stub! --- snip --- * https://source.winehq.org/git/wine.git/commitdiff/48bcae100eea82ce0199c40d37... ("d2d1: Return S_OK from RegisterEffectFromString().") Client area renders fine but no UI interaction possible. Text boxes (bounding rectangles) are not drawn and as soon as the document is clicked/resized, the client area is rendered black again. * https://source.winehq.org/git/wine.git/commitdiff/0ab71185034a065d1e6161b722... ("d2d1: Return S_OK from d2d_effect_SetValue().") UI interaction now possible, including menu selection, window resize etc. Text boxes (bounding rectangles) are drawn. Mouse cursor/shape remains invisible. The mouse cursor became visible with non-Direct2D commit but dxgi: * https://source.winehq.org/git/wine.git/commitdiff/2ea796ad71d81503b5e84bc248... ("dxgi: Support IID_IDXGIDevice in dxgi_adapter_CheckInterfaceSupport().") All part of Wine 3.19 release. Resolving 'FIXED'. $ wine --version wine-6.0-rc4 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44574 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.0-rc5. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla