wine-bugs December 2019

wine-bugs@winehq.org

1 participants
7436 discussions

[Bug 48180] New: Divinity: Original Sin 2 - Icons in inventory are invisible
by WineHQ Bugzilla 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48180 Bug ID: 48180 Summary: Divinity: Original Sin 2 - Icons in inventory are invisible Product: Wine Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: apmichalopoulos(a)outlook.com Distribution: --- Created attachment 65815 --> https://bugs.winehq.org/attachment.cgi?id=65815 Game running inside a clean 4.19 prefix As per title, after upgrading to Wine 4.20, the game's inventory icons are completely invisible. Everything else, including all other icons (in hotbars, in portraits, while dragging and dropping, in containers or while trading with vendors, etc), works like a charm. Downgrading to 4.19 fixes the issue. Also, I don't know what the policy about mentioning wine-staging is in this bug tracker, but I tested with it as well and it also works in 4.19 while it breaks in 4.20, so this seems to be a mainstream Wine bug. -- 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 18

[Bug 34232] New: Rigs of Rods: dropdown menus have too small height
by wine-bugs＠winehq.org 27 Dec '19

27 Dec '19

http://bugs.winehq.org/show_bug.cgi?id=34232 Bug #: 34232 Summary: Rigs of Rods: dropdown menus have too small height Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Classification: Unclassified Created attachment 45546 --> http://bugs.winehq.org/attachment.cgi?id=45546 How it looks in wine See the screenshot attached. The combobox dropdown menu is denoted by red arrow. Because of this it looks as if there were only a single entry while there are more. And this reproduces with most of dropboxes in the app. -- 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.

2 11

[Bug 39084] New: Simpsons Hit & Run regression: fullscreen glitching
by wine-bugs＠winehq.org 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=39084 Bug ID: 39084 Summary: Simpsons Hit & Run regression: fullscreen glitching Product: Wine Version: 1.7.49 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: V02460(a)gmail.com Distribution: Fedora Created attachment 52074 --> https://bugs.winehq.org/attachment.cgi?id=52074 Run with glitching fullscreen on 1.7.49 The game starts fine in fullscreen mode on the current stable wine version (1.6.2) On the current version of wine the game has issues when started in fullscreen mode. When started it tries to go fullscreen but reverts to the desktop as a black windows with glitched decorations. Workaround: One way to get the game started is to switch to a different (gnome) desktop and back twice(!). Only then the intro starts playing and the main menu appears. It should be noted by using this method it only gets me a maximized window with changed screen resolution. It is still possible to get the game into real fullscreen mode by doing the above workaround, closing the game, not changing focus (aka not clicking somewhere with the mouse) and starting the game again. Command used to start the game: taskset -c 0 wine Simpsons.exe -- 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.

2 8

[Bug 14901] New: MoveFile fails when used to recase some letters of the filename
by wine-bugs＠winehq.org 27 Dec '19

27 Dec '19

http://bugs.winehq.org/show_bug.cgi?id=14901 Summary: MoveFile fails when used to recase some letters of the filename Product: Wine Version: 1.1.2 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: redneb(a)mailinator.com When my program executes the MoveFile windows API function having as arguments two strings that are equal (in a case insensitive way) then MoveFile fails and GetLastError returns 183 (i.e. "File already exists"). For example, assume that the current directory contains a file "foobar". If you run MoveFile("foobar","Foobar") you will get the above error. On the contrary this works fine under windows. Even MoveFile("foobar","foobar") works under windows. I have tested that with 0.9.61/1.1.0/1.1.2 (under Gentoo) and 1.0.0 (under Ubuntu). -- 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.

2 46

[Bug 48368] New: an odd quirk of focus handling while managed by window manager
by WineHQ Bugzilla 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48368 Bug ID: 48368 Summary: an odd quirk of focus handling while managed by window manager Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Description is simple, problem - not so much. Let's take three windows: - first is a random wine app 1 - second is a terminal window used to start random wine app 2 (but not a wine window) - third is random app 2 Now lets place those windows on top of each other in that order so that close button of random app 2 is contained within the second window. Now, let's press that close button. What happens: - third window closes (WASD) - second window gets keyboard/visible focus (pretty much as above) - first window doesn't get *visible* focus, but acts as if it had gotten mouse focus (for example if random app 1 has a setting "pause while not focused", it's getting unpaused) ... huh ? That last part seems quite buggy... -- 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 0

[Bug 44393] New: cannot read form named pipe in wine 3.0 after bug fix 43217
by wine-bugs＠winehq.org 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=44393 Bug ID: 44393 Summary: cannot read form named pipe in wine 3.0 after bug fix 43217 Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: luca.cunegondi(a)ocme.com Distribution: --- a commercial cad application has commands that can read directly from named pipe if file name starts with a '|'. Example: open_infile '| /usr/bin/ls /tmp | grep pdf' read_file ... This worked perfectly until wine 2.17 and wine-staging 2.18 (on Arch Linux), then stopped working due to bug 43217 and persists after the bug fix. Enabling trace+process debug option shows a call to create_process_impl (wine 3.0) instead of CreateProcessInternalW as before -- 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.

2 19

[Bug 48366] New: Wine 5.0-rc2 for Android is built with a very obsolete Android SDK and doesn't work properly on Android 10
by WineHQ Bugzilla 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48366 Bug ID: 48366 Summary: Wine 5.0-rc2 for Android is built with a very obsolete Android SDK and doesn't work properly on Android 10 Product: Packaging Version: unspecified Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: vyproyects(a)gmail.com CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 66109 --> https://bugs.winehq.org/attachment.cgi?id=66109 Warning dialogs on Android 10 Wine 5.0-rc2 APKs for ARM and x86 are built with a very obsolete SDK for Android API Level 25 (Android 7.1) which is compileSdkVersion tag Also targetSdkVersion tag appears to be below 23 as it doesn't ask for permissions during runtime on Android 6.0+ and it asks for them on Android 10 at start (new security feature on Android 10): https://developer.android.com/about/versions/10/behavior-changes-all#low-ta…. This is an attached image. Besides during start a dialog appears warning that it is built for an old version of android, also attached as image. I have tested on an Android 10 AVD emulator with x86 CPU architecture. But also have opened both APKs to check their compile and target SDK versions. Furthermore it crashes after extracting files. This outdated packaging appears to be the cause although android 10 includes some changes to NDK for all apps even when targeting an old version what may be the cause: https://developer.android.com/about/versions/10/behavior-changes-all#q-ndk In conclusion Wine for android needs a deep upgrading. -- 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 48364] New: Clifford Thinking Adventures fails to start in some configurations
by WineHQ Bugzilla 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48364 Bug ID: 48364 Summary: Clifford Thinking Adventures fails to start in some configurations Product: Wine Version: 5.0-rc2 Hardware: x86 OS: Linux Status: NEW Keywords: patch Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 66108 --> https://bugs.winehq.org/attachment.cgi?id=66108 gdi32: Return the current display frequency from GetDeviceCaps(VREFRESH). It spews out a message box saying: "This program cannot be run with your current monitor settings. Please reset your monitor to a minimum of 256 colors before running Clifford." In fact an 8-bit display device isn't necessary. What is necessary is for EnumDisplaySettings() to return at least one device with a refresh rate equal to the number returned by GetDeviceCaps(VREFRESH). Under normal circumstances the latter returns 1, but the former may return e.g. 60. The attached patch fixes this, and makes the game completely playable for me. -- 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 4

[Bug 43021] New: I Spy Spooky Mansion black screen, silent
by wine-bugs＠winehq.org 27 Dec '19

27 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=43021 Bug ID: 43021 Summary: I Spy Spooky Mansion black screen, silent Product: Wine Version: 2.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- When run, the game presents an entirely black screen with no sound. Pressing Escape will close the game. On Windows, starting the game plays a series of animations with sound (Scholastic logo, etc.) The only lines of console output are this: err:ole:CoGetClassObject class {e78f7620-96cb-11cf-a00b-444553540000} not registered err:ole:CoGetClassObject no class object {e78f7620-96cb-11cf-a00b-444553540000} could be created for context 0x1 however, these CLSIDs are not registered on Windows either, so this is probably a red herring. -- 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.

2 1

[Bug 46376] New: Touhou 10 on macOS 10.13.6 (High Sierra) may crash or freeze on startup after Security Update 2018-003
by wine-bugs＠winehq.org 26 Dec '19

26 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=46376 Bug ID: 46376 Summary: Touhou 10 on macOS 10.13.6 (High Sierra) may crash or freeze on startup after Security Update 2018-003 Product: Wine Version: 4.0-rc3 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrewsuicune(a)gmail.com When testing Touhou 10 - Mountain of Faith for the 4.0 release candidates, I noticed that the game began crashing/freezing, mainly during Fullscreen. None of the other games in the series I had tested recently exhibited this issue and this particular installment had never done this kind of behavior. Worse, it was difficult to replicate because a freeze during fullscreen mode required forcefully killing the OS and rebooting the machine since all other I/O other than hard reset are blocked by Wine. Though this happened on 4.0 rc3, I went back to Wine 3.11 and tried it out again. I was able to freeze the OS simply by selecting Fullscreen and doing *nothing* but wait for the main menu. On 4.0 rc3 Fullscreen, hitting the down arrow key on the "Press Any Key" screen causes Wine to crash with the following: wine: Unhandled page fault on read access to 0x1102983d at address 0x7bc40a7b (thread 0061), starting debugger... 0061:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc406db ~~~~~ I have not classified this as a regression since every other Touhou game I've tested has not exhibited this issue and since the game was working fine (afaik) on 3.11 when I tested it way back then but no longer functions when I run 3.11 now, implying that something other than the Wine updates broke. My suspicion is that something in the latest macOS High Sierra security update broke something with the way Wine works with this specific application. If possible, I'd like the following to be tested: - First, if someone else can replicate the crash on Wine 3.11 using macOS High Sierra 10.13.6 with Security Update 2018-003. - Next, if possible, for the same to be attempted on macOS High Sierra 10.13.6 without Security Update 2018-003 (though this may be difficult or impossible to do) If the macOS update was what broke the game, then this is *probably* not a Wine bug. If it's broken on Wine 3.11 and pre-Security Update 2018-003 macOS High Sierra, then further investigation may be required as to why the game was working fine back in June but no longer functions now. Once the game is running (IE if you can actually get through the menus without the game crashing/freezing), things seem to be fine from that point onwards, though I am unable to definitively confirm this. -- 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.

2 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2019