https://bugs.winehq.org/show_bug.cgi?id=46666
Bug ID: 46666
Summary: Al Unser, Jr Arcade Racing has weird colors
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: haakobja(a)gmail.com
Distribution: ---
Created attachment 63612
--> https://bugs.winehq.org/attachment.cgi?id=63612
Screenshot showing wrong colors
Hi,
I have recently tried Al Unser, Jr. Arcade Racing with Wine, the game itself is
from 1995 so its is quite old. I was just curious. I have managed to get the
game working, but the colors is not right. The game requires an 8 bit display,
otherwise it refuses to start.
I followed the recommendations and used the following commands:
$ Xephyr :1 -screen 800x600x8 -cc 3 &
$ DISPLAY=:1 wine alunser.exe
The game starts, but the colors are wrong. As displayed in my attached image.
A demo, which displays the same colors, are available at:
https://archive.org/details/Alunser. There's also an image displaying the
colors as they should be.
--
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=56232
Bug ID: 56232
Summary: Sega Bug fails to initialize
Product: Wine
Version: 3.17
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 75943
--> https://bugs.winehq.org/attachment.cgi?id=75943
WINEDEBUG=+d3d,+ddraw
Steps to reproduce:
1. Insert the Sega Bug CD
2. Run `Xephyr :1 -ac -screen 800x600x8 &`
3. Run `DISPLAY=:1 openbox &`
4. Run `DISPLAY=:1 wine 'D:\win95\bug!.exe'`
An error dialog titled "Error Initialising" appears that says "A hardware-only
DirectDraw object creation was attempted but the driver did not support any
hardware." After clicking OK, a second dialog appears that says "Could not
initialise DirectDraw".
I have a patch that I could apply to Wine < 3.17 to get the game to work, but
this error is relatively new. `git bisect` says:
7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b is the first bad commit
commit 7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b
Author: Józef Kucia <jkucia(a)codeweavers.com>
Date: Mon Sep 24 01:09:31 2018 +0200
wined3d: Pass feature levels to wined3d_device_create().
Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Debug traces are attached. I believe the relevant line is:
0024:warn:ddraw:ddraw_surface_create Video memory surfaces not supported
without 3D support.
--
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=47490
Bug ID: 47490
Summary: GlobalLock different behavior
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: ghotik2002(a)yahoo.com
Distribution: ---
Different behavior of GlobalLock in DxWnd GUI routine.
This is an extract of source code:
IStream *pStream = 0;
CreateStreamOnHGlobal(0, TRUE, &pStream);
LONG cbSize = 0;
hr = pPicture->SaveAsFile(pStream, TRUE, &cbSize);
if(FAILED(hr)) {
OutTrace("GrayIcon: SveAsFile error hr=%#x\n", hr);
return NULL;
}
HGLOBAL hBuf = 0;
hr = GetHGlobalFromStream(pStream, &hBuf);
if(FAILED(hr)) {
OutTrace("GrayIcon: GetHGlobalFromStream error hr=%#x\n", hr);
return NULL;
}
buf = (BYTE *)GlobalLock(hBuf);
if(buf == NULL) {
OutTrace("GrayIcon: GlobalLock error err=%d\n", GetLastError());
return NULL;
}
the stream holds an icon picture, everything is ok but the GlobalLock call:
- in Windows it returns a valid memory address
- in Wine/Linux it returns NULL errno 157 ERROR_DISCARDED - The segment is
already discarded and cannot be locked.
All this is in DxWnd program run on Wine/Linux environment.
P.s. my first bug report here - hope everything is more or less ok ... ;)
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=55167
Bug ID: 55167
Summary: Spotify crashes when trying to install
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: just4steam778(a)gmail.com
Distribution: ---
Created attachment 74747
--> https://bugs.winehq.org/attachment.cgi?id=74747
Launch log
I'm trying to install the Windows version of Spotify and it immediately crashes
when I launch the executable.
Wine build: wine-8.11-125-g3d28f9d362e
OS: Arch Linux
--
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=56272
Bug ID: 56272
Summary: Missing axes and buttons from Turtle beach flightstick
yoke
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: keri24601(a)yahoo.com
Distribution: ---
Created attachment 75993
--> https://bugs.winehq.org/attachment.cgi?id=75993
screenshot of control.exe and jstest
jstest-gtk correctly identifies the yoke as having 10 axes and 34 buttons.
Running in wine with control.exe, there's only 4 working axes + 2 of them that
overlap, with 10 buttons and, one of the hats work.
The wine version is 9.0
--
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=55470
Bug ID: 55470
Summary: i686-w64-mingw32-gcc assumes wrong stack alignment
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: stefan(a)codeweavers.com
Distribution: ---
Created attachment 75028
--> https://bugs.winehq.org/attachment.cgi?id=75028
Example C code to show the issue
This is probably not a Wine bug, but something we may want to document and take
care of one way or another:
i686-w64-mingw32-gcc quietly assumes 16 byte stack alignment, which is wrong
for Win32. To see the effect compile and disassemble the attached test.c with
i686-w64-mingw32-gcc test.c -c -O2
i686-w64-mingw32-objdump -d test.o
The outcome:
0: 81 ec ac 01 00 00 sub $0x1ac,%esp
6: 8d 44 24 10 lea 0x10(%esp),%eax
a: 89 04 24 mov %eax,(%esp)
d: e8 00 00 00 00 call 12 <_func+0x12>
12: 81 c4 ac 01 00 00 add $0x1ac,%esp
18: c3 ret
However, x86_64-w64-mingw32-gcc -m32 properly aligns the stack before placing
the aligned structure:
x86_64-w64-mingw32-gcc test.c -c -O2 -m32
i686-w64-mingw32-objdump -d test.o
0: 55 push %ebp
1: 89 e5 mov %esp,%ebp
3: 83 e4 f0 and $0xfffffff0,%esp
6: 81 ec a0 01 00 00 sub $0x1a0,%esp
c: 8d 44 24 10 lea 0x10(%esp),%eax
10: 89 04 24 mov %eax,(%esp)
13: e8 00 00 00 00 call 18 <_func+0x18>
18: c9 leave
19: c3 ret
To my knowledge Wine does not use SSE instructions on purpose, so we should be
mostly fine. msvcrt, wined3d or dsound (especially when compiled to use SSE to
make Rosetta 2 happy) may be affected.
The test.c file is attached.
What can we do about it?
1) Ignore it
2) pass -mincoming-stack-boundary=2 to mingw for 32 bit targets
3) Use 64 bit target mingw with -m32
I'll file a bug for mingw too, linking this bug as reference.
--
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=56216
Bug ID: 56216
Summary: Wine 9.0 Wayland cursor does not hide when holding
mouse button on game world to move camera/character
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yaomtc(a)protonmail.com
Distribution: ---
I have tested this with Final Fantasy XIV.
In FFXIV, intended behavior is for the cursor to be hidden while holding down
the left and/or right mouse button to move the camera and/or your character. It
does not, it just locks in place (good, but it should be invisible too). This
works correctly with X11 or XWayland, but with the experimental Wayland driver,
the cursor does not hide.
--
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=55041
Bug ID: 55041
Summary: QuickTime movie plays but screen is black
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mildred-bug.winehq(a)mildred.fr
Distribution: ---
When running "The Wheel of Time"
https://appdb.winehq.org/objectManager.php?sClass=version&iId=2154 cutscenes
will play but the screen stays black. It uses QuickTime Lite 4.1.0 for movies.
Using wayland (SwayWM)
During movie playback, I see the following log repeated:
0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 70c00 (device=7 access=0
func=300 method=0)
There is in a forum someone that had a similar issue and found a solution
(translated by me):
> I think the problem comes from QuickTime, the software installs version 7.2
> Via wine control, I disabled directx for the video and set up safe move (GDI only)
> It seems to hold, I must test again to be sure.
> The issue really came from quicktime and my change solved the issue.
>
> https://forum.ubuntu-fr.org/viewtopic.php?id=389950
I tried winetricks render=nod3d or render=gdi but it does not help.
--
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=55589
Bug ID: 55589
Summary: Tomb Raider: Legend has black/blue artifacts
Product: Wine
Version: 6.22
Hardware: x86-64
URL: https://www.moddb.com/games/tomb-raider-legend/downloa
ds/tomb-raider-legend-updated-demo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: matteo.mystral(a)gmail.com
Regression SHA1: 884b7c50cfd902eff9a41562a103e3bd5747422b
Distribution: ---
Created attachment 75116
--> https://bugs.winehq.org/attachment.cgi?id=75116
example
After enabling 'Next generation content' in Options -> Display.
--
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.