wine-bugs July 2020

1 participants
6685 discussions

[Bug 49489] New: Regression - b86dc3926bfe5cd92400aa96c89b0255eba1d447 causes incorrect rendering in Warframe with nvidia

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49489 Bug ID: 49489 Summary: Regression - b86dc3926bfe5cd92400aa96c89b0255eba1d447 causes incorrect rendering in Warframe with nvidia Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67611 --> https://bugs.winehq.org/attachment.cgi?id=67611 warframe incorrect rendering On a clean prefix with a new Warframe installation, incorrect rendering occurs (see image) with Nvidia gpus. This has been bisected to wine commit: https://github.com/wine-mirror/wine/commit/b86dc3926bfe5cd92400aa96c89b0255… This works on AMD with both wined3d and vkd3d, but renders incorrectly on Nvidia -- 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.

3 years, 10 months

[Bug 49438] New: Wine on ARM64 fails with "could not exec the wine loader" unless --enable-win64 is used

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49438 Bug ID: 49438 Summary: Wine on ARM64 fails with "could not exec the wine loader" unless --enable-win64 is used Product: Wine Version: 5.11 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com Distribution: --- I've been building Wine on ARM64 (Ubuntu 19.10 64-bit on Raspberry Pi 4). Since 67bc4a6d765941d830477f749ab7b0697f1488b2 ("ntdll: Don't use libwine during the Unix library initialization."), Wine fails with "could not exec the wine loader" unless '--enable-win64' is passed to configure. Before that commit, I was using configure without any options. The problem looks to be that in dlls/ntdll/unix/server.c, 'loader/wine64' or 'loader/wine' is chosen based on the size of a pointer (is_win64). And unless '--enable-win64' is used, 'loader/wine' is built, but it tries to exec 'loader/wine64'. I'm not sure what the best fix for this is. Require a win64 build when 64-bit code is being built? The 'configure' help text should also be updated. Configure options now needed: './configure --enable-win64 CC=clang' -- 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.

3 years, 10 months

[Bug 49422] New: Dungeon Siege 1 & 2 weapon misplacement

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49422 Bug ID: 49422 Summary: Dungeon Siege 1 & 2 weapon misplacement Product: Wine Version: 5.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: loentar(a)gmail.com Distribution: --- Created attachment 67502 --> https://bugs.winehq.org/attachment.cgi?id=67502 ds1 screenshot with bow Any weapon equipped to the character is placed wrongly. It appear on the ground instead of character hands. That wasn't reproducible in wine 4. Reproducible for: original Dungeon Siege 1 CD, original Dungeon Siege 1 Steam Version, Dungeon Siege 1 Demo, Dungeon Siege 1 Legends of Arrana, Dungeon Siege 2 (DVD), Dungeon Siege 2 Broken World. Wine versions: 5.10, 5.11 (I didn't tested other 5.x versions) Ubuntu 20.04, 16.04 -- 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.

3 years, 10 months

[Bug 31023] New: CuteFTP 8.3.4 - "Encountered an improper argument." Error boxes after most actions.

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=31023 Bug #: 31023 Summary: CuteFTP 8.3.4 - "Encountered an improper argument." Error boxes after most actions. Product: Wine Version: 1.5.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nicekiwi(a)gmail.com Classification: Unclassified Created attachment 40721 --> http://bugs.winehq.org/attachment.cgi?id=40721 debug logfile Interacting with most buttons and will cause at least one popup box with the text "Encountered an improper argument.". -- 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.

3 years, 10 months

[Bug 36546] New: Please remove `tmpfs` special treatment in ntdll

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36546 Bug ID: 36546 Summary: Please remove `tmpfs` special treatment in ntdll Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com I do love running Wine in /tmp which is mounted as `tmpfs` in my Linux. However every other application installer whines that disk C: is not local so I have to use tricks to force applications to install in a WINEPREFIX which is located in RAM. Please, remove the special treatment of tmpfs mount points. -- 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.

3 years, 10 months

[Bug 49580] New: When ending the program SiDiary with the "X" i get an error message

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49580 Bug ID: 49580 Summary: When ending the program SiDiary with the "X" i get an error message Product: Wine Version: 5.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: erich.z(a)gmx.net Distribution: --- Created attachment 67732 --> https://bugs.winehq.org/attachment.cgi?id=67732 File generated by wine Unhandled exception: page fault on read access to 0x7d587b40 in 32-bit code -- 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.

3 years, 10 months

[Bug 47409] New: odd behavior in several apps changing resolution after a crash

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=47409 Bug ID: 47409 Summary: odd behavior in several apps changing resolution after a crash Product: Wine Version: 4.11 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: --- To make a thing clear: this isn't a GPU driver problem, over the years, I've seen this happen with a few different graphic cards using different drivers; also, while I'm opening this only now, the problem might be already over a decade old, just hard to trigger/notice, unless you're looking for it. If an app that changes resolution crashes during resolution change, *some* of the time it leaves xserver in an inconsistent state, where despite running 'xrandr -s <foo>', the app that crashed can't be started again until xserver restart (as simply shutting down whole wine doesn't work). If I start a second instance of the server, the app will start there without a problem there (that is, if no other problem occurs), but that leads to a different problem: if there are other wine apps running on the first display, another xerror triggered crash might happen. Due to excessive randomness involved (and the need to trigger a crash in the first place), this is hard to reproduce *exactly*, yet in the past years I've seen it quite a few times. Also, to make it clear, I've seen this in many unrelated apps, their only common theme was changing resolution (and perhaps using directdraw, but I'm not sure about this part). Also, while not sure about it, IIRC, all of those apps didn't change the res back upon Alt-Tab - for some reason, I think this might be important. xerror in the first case: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Value in failed request: 0x0 Serial number of failed request: 438 Current serial number in output stream: 439 xerror in the second case: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 10 (X_UnmapWindow) Resource id in failed request: 0x4c00003 Serial number of failed request: 322 Current serial number in output stream: 325 In the second case, it might simply be that wine caches DISPLAY value somewhere in the driver and tries to access first display with the resolution change, but no idea what's the first case, if xrandr is insufficient for a reset. -- 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.

3 years, 10 months

[Bug 49554] New: Vape v4: Has a serious problem when trying to inject into Minecraft

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49554 Bug ID: 49554 Summary: Vape v4: Has a serious problem when trying to inject into Minecraft Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: ell88qwanon8(a)protonmail.com Distribution: --- Wine tells me that the program vapev4.exe has encountered a serious problem and needs to close when I try to inject it into Minecraft. About Vape v4: It's a PAID Minecraft cheat client made for 64-bit Windows. -- 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.

3 years, 10 months

[Bug 49533] New: Winetricks -q dotnet45 does not work

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49533 Bug ID: 49533 Summary: Winetricks -q dotnet45 does not work Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: --- Since update of wine-5.12,dotnet45 fails to install (looks like installer entered in an infinite loop). As dotnet45 does not install with wine only (needs winetricks) I was unable to perform a regression test. -- 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.

3 years, 10 months

[Bug 49525] New: Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49525 Bug ID: 49525 Summary: Battle.net launcher fails to launch games with "ClientSdk.dll" failed to initialize error Product: Wine-staging Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matthew4196(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Since wine-staging 5.12, the Battle.net launcher is failing to launch some games and is getting error "04c4:err:module:LdrInitializeThunk "ClientSdk.dll" failed to initialize, aborting". With wine-staging 5.3, 5.9 - 5.11, both Warcraft III and Starcraft I are able to launch. Vanilla wine 5.1, 5.9 - 5.12 all appear to fail with the same ClientSdk.dll error. -- 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.

3 years, 10 months

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 July 2020