wine-bugs February 2024

wine-bugs@winehq.org

1 participants
1505 discussions

[Bug 41930] New: Civilization III Complete shows black terrain ( Wine compiled with OSMesa support)
by wine-bugs＠winehq.org 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=41930 Bug ID: 41930 Summary: Civilization III Complete shows black terrain (Wine compiled with OSMesa support) Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: michael(a)fds-team.de Regression SHA1: e618ab65ed5b623785c58ea5ece6e39895d43063 Distribution: --- Created attachment 56311 --> https://bugs.winehq.org/attachment.cgi?id=56311 screenshot This is one of the few games that I know of which makes some use of OpenGl in bitmaps. When Wine was compiled with OSMesa support, tiles containing terrain turn black as soon as I launch a game. Reproduced with Nvidia binary drivers 375.20 and nouveau/mesa. I tried Civilization III Complete (both the Steam and the GOG.com versions have this bug). Terminal output: fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 err:ole:CoGetClassObject class {5959df60-2911-11d1-b049-0020af30269a} not registered err:ole:CoGetClassObject no class object {5959df60-2911-11d1-b049-0020af30269a} could be created for context 0x1 Reverting the following patch on top of git fixes the problem: commit e618ab65ed5b623785c58ea5ece6e39895d43063 Author: Michael Müller <michael(a)fds-team.de> Date: Tue Feb 3 11:07:38 2015 +0100 gdi32: Fix arguments for OSMesaMakeCurrent when using 16 bit formats. Please let me know if you need debug logs. wine-1.9.24-105-g1d3b944 Fedora 24 x86_64 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 375.20 Installed packages: mesa-libOSMesa.i686 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa.x86_64 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa-devel.i686 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa-devel.x86_64 13.1.0-0.12.git95ddb37.fc24 -- 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 71

[Bug 56279] New: Wine fails to build if CC is set to the absolute path for the compiler
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56279 Bug ID: 56279 Summary: Wine fails to build if CC is set to the absolute path for the compiler Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vibhavp(a)gmail.com Distribution: --- At least as of commit e607da943aa (win32u: Only queue a single IME update during ImeProcessKey.), the Wine build fails if any of the [<ARCH>_]CC environment variables are set to an absolute path to GCC/Clang, as opposed to just the executable name. This can be reproduced by configuring and building Wine with the follow environment variables: export CC='/usr/bin/gcc' export CROSSCC='/usr/bin/i686-w64-mingw32-gcc' export i386_CC='/usr/bin/i686-w64-mingw32-gcc' export x86_64_CC='55/usr/bin/x86_64-w64-mingw32-gcc' The failure is specifically due to winebuild being provided an invalid target specification argument (in this case, `/usr/bin/i686-w64-mingw32` instead of `i686-w64-mingw32` ): tools/winebuild/winebuild -w --staticlib -o dlls/winecrt0/i386-windows/libwinecrt0.a -b /usr/bin/i686-w64-mingw32 \ ... winebuild: Unrecognized target '/usr/bin/i686-w64-mingw32' make: *** [Makefile:167493: dlls/winecrt0/i386-windows/libwinecrt0.a] Error 1 -- 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 51537] New: Mouse does not work in civilization VI
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=51537 Bug ID: 51537 Summary: Mouse does not work in civilization VI Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: voker57(a)gmail.com Distribution: --- Created attachment 70376 --> https://bugs.winehq.org/attachment.cgi?id=70376 complete log Mouse does not work in Sid Meier's Civilization VI, menu loads but it is not possible to do anything further. This comment https://bugs.winehq.org/show_bug.cgi?id=49315#c9 suggests a cause of this 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 7

[Bug 56268] New: The XM1 Configuration Software doesn't detect the mouse
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56268 Bug ID: 56268 Summary: The XM1 Configuration Software doesn't detect the mouse Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bq74stlxvkpb(a)opayq.com Distribution: --- Created attachment 75985 --> https://bugs.winehq.org/attachment.cgi?id=75985 XM1 RGB isn't detected by its configuration application When attempting to modify the firmware of an XM1 RGB mouse, the configuration tool fails to detect it. The tool can be freely downloaded at: https://www.endgamegear.com/en-us/downloads/xm1rgb The downloaded file should be XM1_RGB_Configuration_Software_(V1.01).zip The installation goes fine. No mouse is detected, however - see the attachment. Under native Win7, the installation fails, so I cannot use that as a workaround. I had to use native Win10 on my work-issued laptop to modify the firmware. Side note - the reason why I am doing this is that the mouse in question, by default, cycles through colours RAPIDLY. It's almost seizure-inducing. I've changed it to solid white. Additional bug I just found out - while the systray icon for it appears while it is running, right-clicking it opens its context menu... behind the taskbar. Furthermore, clicking elsewhere doesn't close its systray icon context menu. -- 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 7

[Bug 30984] New: Some keys do not work in Trine and Skyrim
by wine-bugs＠winehq.org 01 Feb '24

01 Feb '24

http://bugs.winehq.org/show_bug.cgi?id=30984 Bug #: 30984 Summary: Some keys do not work in Trine and Skyrim Product: Wine Version: 1.5.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: yves.embil(a)orange.fr Classification: Unclassified Regression SHA1: 43984f355a2905e16075a9df3d7fbe463761e853 Created attachment 40666 --> http://bugs.winehq.org/attachment.cgi?id=40666 result of the regression test In Trine the key to select the thief and Skyrim the key to open the console does not work,with wine-1.5.5 it works. -- 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 67

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 February 2024