August 2018 - Wine-Bugs - list.winehq.org

[Bug 12553] New: Toolbars misplaced, hidden
by wine-bugs＠winehq.org Aug. 17, 2018

Aug. 17, 2018

http://bugs.winehq.org/show_bug.cgi?id=12553 Summary: Toolbars misplaced, hidden Product: Wine Version: 0.9.59. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tarasov.igor(a)gmail.com Created an attachment (id=12122) --> (http://bugs.winehq.org/attachment.cgi?id=12122) WINEDEBUG=+toolbar,+listview,+themingcombo wine 0.9.59 log Here are two screenshots: Wine being run with MS comctl32.dll, the same thing you see in Windows: http://polosatus.ru/wine/toolbar_reference.png And wine running with it's own version of comctl32: http://polosatus.ru/wine/toolbar_bug.png First of all, disappeared toolbar at the middle of screenshot. Also, notice misplaced right toolbar. It is misplaced to left a bit. I suppose both bugs are related. Seems that developers have used some undocumented features, as log has this: warn:toolbar:TOOLBAR_SetBitmapSize 5 buttons, undoc increase to bitmap size : 16-15 -> 20-20 and this: warn:toolbar:TOOLBAR_SetBitmapSize 6 buttons, undoc increase to bitmap size : 20-20 -> 16-16 several times. I've supposed that WINEDEBUG=+toolbar,+listview,+themingcombo should be enough for initial log :) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 42

[Bug 45651] New: Dark Souls 3: The Ringed City crashes
by wine-bugs＠winehq.org Aug. 16, 2018

Aug. 16, 2018

https://bugs.winehq.org/show_bug.cgi?id=45651 Bug ID: 45651 Summary: Dark Souls 3: The Ringed City crashes Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: godevilove(a)ya.ru Distribution: --- Created attachment 62080 --> https://bugs.winehq.org/attachment.cgi?id=62080 Crash log I played like 5 min, killed a few monsters, died, respawned, went killing again and it then first froze for like 5 second and then in 10 second it froze and crashed. OS: XUbuntu 18.04, GPU: nvidia gtx970, Kernel: linux-image-generic/bionic-updates,bionic-security,now 4.15.0.30.32 amd64 [installed,automatic] Packages: wine-staging/bionic,now 3.13.0-2~bionic amd64 [installed,automatic] wine-staging-amd64/bionic,now 3.13.0-2~bionic amd64 [installed,automatic] wine-staging-i386/bionic,now 3.13.0-2~bionic i386 [installed,automatic] winehq-staging/bionic,now 3.13.0-2~bionic amd64 [installed] winetricks/bionic,bionic,now 0.0+20180217-1 all [installed] nvidia-compute-utils-390/bionic,now 390.48-0ubuntu3 amd64 [installed,automatic] nvidia-dkms-390/bionic,now 390.48-0ubuntu3 amd64 [installed,automatic] nvidia-driver-390/bionic,now 390.48-0ubuntu3 amd64 [installed] nvidia-kernel-common-390/bionic,now 390.48-0ubuntu3 amd64 [installed,automatic] nvidia-kernel-source-390/bionic,now 390.48-0ubuntu3 amd64 [installed,automatic] nvidia-prime/bionic,bionic,now 0.8.8 all [installed,automatic] nvidia-settings/bionic,now 390.42-0ubuntu1 amd64 [installed,automatic] nvidia-utils-390/bionic,now 390.48-0ubuntu3 amd64 [installed,automatic] Wineprefix: clean, compatibility with Windows XP. The game also was pretty low fps :( -- 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.

1 3

[Bug 45230] New: wine 3.8: gdi32.dll failed to initialize
by wine-bugs＠winehq.org Aug. 16, 2018

Aug. 16, 2018

https://bugs.winehq.org/show_bug.cgi?id=45230 Bug ID: 45230 Summary: wine 3.8: gdi32.dll failed to initialize Product: Wine Version: 3.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: countstarlight(a)gmail.com Distribution: --- Created attachment 61460 --> https://bugs.winehq.org/attachment.cgi?id=61460 wine error log System: Archlinux wine: 3.8 Upgrade wine from 3.7 to 3.8, the installed application not work. The Archlinux aur package repository at https://github.com/countstarlight/deepin-wine-tim-arch, and log in attachment After downgrading wine to version 3.7, the application can work, and not see "gdi32" in log. -- 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.

1 14

[Bug 45637] New: KOMPAS 3D viewer V17: failure to repaint the 3D models
by wine-bugs＠winehq.org Aug. 15, 2018

Aug. 15, 2018

https://bugs.winehq.org/show_bug.cgi?id=45637 Bug ID: 45637 Summary: KOMPAS 3D viewer V17: failure to repaint the 3D models Product: Wine Version: 3.13 Hardware: x86 URL: http://download.ascon.ru/public/Viewer_v17.1/x86/viewe r_V17.1_x86.7z OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru Distribution: --- Steps to reproduce: 1. winetricks -q dotnet452 2. run winecfg and change the reported version back to Windows 7 3. download and unpack http://download.ascon.ru/public/Viewer_v17.1/x86/viewer_V17.1_x86.7z 4. install the application using Setup.exe 5. cd '~/.wine/drive_c/Program Files/ASCON/KOMPAS-3D Viewer v17/Bin' 6. wine kViewer.Exe 7. load the sample model and move the mouse around, there are a lot of failures to repaint the 3D model. -- 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.

1 1

[Bug 45606] New: eGames New Collection! Solitaire Master 2: wine crash error on closing
by wine-bugs＠winehq.org Aug. 12, 2018

Aug. 12, 2018

https://bugs.winehq.org/show_bug.cgi?id=45606 Bug ID: 45606 Summary: eGames New Collection! Solitaire Master 2: wine crash error on closing Product: Wine Version: 3.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: daveypy(a)outlook.com Distribution: --- Created attachment 62036 --> https://bugs.winehq.org/attachment.cgi?id=62036 Backtrace saved from crash Wine error (see backtrace). Note: I would like to try the development Wine release (to help with bug reporting), but I would prefer to keep the stable version, to avoid regressions. I'm not an experienced bug reporter. -- 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.

1 2

[Bug 40412] New: When opening the game Stardew Valley, I get an error message and it never opens
by wine-bugs＠winehq.org Aug. 12, 2018

Aug. 12, 2018

https://bugs.winehq.org/show_bug.cgi?id=40412 Bug ID: 40412 Summary: When opening the game Stardew Valley, I get an error message and it never opens Product: Wine Version: 1.9.4 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: goodman.jaime(a)gmail.com Created attachment 54149 --> https://bugs.winehq.org/attachment.cgi?id=54149 backtrace file I get the message "This program has encountered a serious problem and needs to close" Logs 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.

1 12

[Bug 45616] New: winecfg: allow setting windows version via CLI
by wine-bugs＠winehq.org Aug. 12, 2018

Aug. 12, 2018

https://bugs.winehq.org/show_bug.cgi?id=45616 Bug ID: 45616 Summary: winecfg: allow setting windows version via CLI Product: Wine Version: 3.13 Hardware: x86 URL: https://github.com/Winetricks/winetricks/blob/master/s rc/winetricks#L2355 OS: Linux Status: NEW Keywords: download, integration, source Severity: enhancement Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo This has been a FIXME in winetricks for years. While reviewing stuff recently, I ran across it and looked into it. I wasn't able to find a (closed) bug for it, and I think it's worth opening one now. Currently, winetricks has to replicate all the logic needed to set a particular Windows version (i.e., major/minor version, service pack version, etc.). This can also include if it's a server version of windows or not, etc. When Wine changes a SP version, winetricks has to catch up later, and it can lead to subtle bugs (e.g., https://github.com/Winetricks/winetricks/issues/970) It would greatly simplify things if instead, winecfg (or some other program, but winecfg seems most appropriate) could change windows versions via a CLI argument. E.g., $ wine winecfg winver=winxp would set winxp mode, and act appropriately for win32/win64. This should return an error if someone tries to set an invalid version, e.g., $ wine winecfg winver=doesnotexist or $ WINEARCH=win64 wine winecfg winver=win98 -- 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.

1 3

[Bug 45614] New: Final Fantasy XIV fails to save its configuration, emptying file instead.
by wine-bugs＠winehq.org Aug. 11, 2018

Aug. 11, 2018

https://bugs.winehq.org/show_bug.cgi?id=45614 Bug ID: 45614 Summary: Final Fantasy XIV fails to save its configuration, emptying file instead. Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spam(a)hjkos.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Link to game https://appdb.winehq.org/objectManager.php?sClass=version&iId=35777 Does not happens with wine-staging 3.12 and the effect is only noticeable after using wine-staging 3.13 once. Tested with both dx11 and dx9 versions of the game, same result. Steps to reproduce: Have game's config data backed up somewhere. Probably backup entire "C:\users\My Documents\My Games\FINAL FANTASY XIV - A Realm Reborn\" folder. Launch the game's launcher using Wine-staging 3.13, Launch the game itself (doesn't matter dx9 or dx11). Wait for game to enter title screen. Click exit. Notice how file "C:\users\My Documents\My Games\FINAL FANTASY XIV - A Realm Reborn\FFXIV.cfg" now is 0 bytes. Same happens to some character data files in FFXIV_CHRxxxxxxx if there are any and you've played as some character with Wine-staging 3.13. There are no errors or warnings in console when write occurs. You can prompt writing FFXIV.cfg on title screen by going into configuration, adjusting some setting and clicking "apply" - on Wine-staging 3.13 file will be emptied. On Wine-staging 3.12 it will be written correctly. Emptying FFXIV.cfg has a nasty side effect in the game that game will launch with "default" configuration - low resolution, ask to calibrate your joystick (even if you don't have one), doesn't remember which server ("data center") you've used, and gets stuck at loading screen right before when character select screen should be. It's possible to exit game normally there by pressing Alt-F4 and confirming exit in dialog window that appears. -- 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.

1 2

[Bug 45604] New: Final Fantasy XIV destroys its own config files on exit after commit 7da7ae7
by wine-bugs＠winehq.org Aug. 11, 2018

Aug. 11, 2018

https://bugs.winehq.org/show_bug.cgi?id=45604 Bug ID: 45604 Summary: Final Fantasy XIV destroys its own config files on exit after commit 7da7ae7 Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: varris(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Relay log (replace <myusername> with a 7 character string if length matters) : https://mega.nz/#!qrAnzaIQ!roWgzw9g99hgtrS9fA_CzK9GHC5_co8rsBCb0fYvOrY How to reproduce: 1. Start Final Fantasy XIV via launcher 2. Immediately exit the game in the main menu 3. At exit, the character specific configuration files are corrupted + FFXIV.cfg is empty. This issue started with commit 7da7ae7. It works fine before that. I've already notified Zebediah Figura about this but I still think it's important to do a proper bug report. Please tell me if you need more information. -- 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.

1 5

[Bug 44597] New: Window rendering com pletely breaks after interacting with the “Desktop Integration” section of winecfg with enabled GTK3 themeing
by wine-bugs＠winehq.org Aug. 10, 2018

Aug. 10, 2018

https://bugs.winehq.org/show_bug.cgi?id=44597 Bug ID: 44597 Summary: Window rendering completely breaks after interacting with the “Desktop Integration” section of winecfg with enabled GTK3 themeing Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexander-winehq(a)xmine128.tk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60584 --> https://bugs.winehq.org/attachment.cgi?id=60584 Changes in HKCU registry # Background & Steps to reproduce Window rendering will show bizare artifacts, up to becoming totally useless (tiny transparent window frames that cannot be interacted with), after following the below steps: 1. In WINE staging enable GTK3 themeing 2. Open `winecfg` again (things should be themed now) 3. Select the “desktop integration” tab 4. Change the “theme” from “GTK-3” to “(No Theme)” and click “Apply” 5. Do the above two times for noticable rendering issues and crashes 6. Do the above three (or more) times to break *any window rendering in WINE* (see attachment 2) # Underlying issue I'm not exactly sure what `winecfg` happens to do here, but it somehow manages to calculate and store some completely wrong values for several entries inside the HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics registry key (see attachment 1) that then result in this behaviour. # Workaround Open `${WINEPREFIX}/user.reg` in a text editor and delete the entire HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics registry key section before launching WINE again. -- 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.

1 2