https://bugs.winehq.org/show_bug.cgi?id=47696
Bug ID: 47696
Summary: EverQuest Started Appearing Upside-Down After Working
Fine for years
Product: Wine
Version: 4.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq.machg(a)spamgourmet.com
Distribution: ---
The game EverQuest used to work great for me on Linux (for years I had no
issue). Ever since my last system update however, the game's visuals appear
inverted/flipped.
What's interesting is that the game still behaves as if the video wasn't
flipped: if I click where a button *should* be, it works. So it seems like the
mouse input layer is working normally, and it's only the video output that has
broken.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35876
Bug ID: 35876
Summary: Hard Reset renders incorrectly with GLSL enabled
Product: Wine
Version: 1.7.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: kmaterka(a)wp.pl
Game renders incorrectly with GLSL enabled. Disabling GLSL lowers amount of
video defects considerably, unfortunately it is not fixing all of them.
Take a look at screenshots submitted here:
http://appdb.winehq.org/screenshots.php?iAppId=13518&iVersionId=25131
Whatever GLSL is enabled or disabled in log you can find a LOT of such errors
(this pack of messages in loop):
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
err:d3d:wined3d_debug_callback 0x2337b80: "GL_INVALID_VALUE error generated.
Point size must not be negative.".
err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from
glPointSize(...); @ state.c / 1568
err:d3d:wined3d_debug_callback 0x2337b80: "GL_INVALID_VALUE error generated.
Point size must not be negative.".
err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from
glPointSize(...); @ state.c / 1568
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
fixme:d3d:gl_stencil_op Unrecognized stencil op 0.
You can download demo using Steam:
http://store.steampowered.com/app/98400/
or from:
http://video.cloudfront.bit-tech.net/bitgamer-demo/hardresetdemo_en.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.
https://bugs.winehq.org/show_bug.cgi?id=47789
Bug ID: 47789
Summary: Gameforge Client: Initialization fails due to
SparkWebHelper.exe crashing
Product: Wine
Version: 4.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sickam(a)mail.ru
Distribution: ---
Created attachment 65278
--> https://bugs.winehq.org/attachment.cgi?id=65278
Wine's terminal output
Hello everyone,
as in the summary stated the Gameforge Client fails to initialize due to
SparkWebHelper.exe crashing. I can click a "retry" symbol in the launcher
afterwards, but it keeps failing again and again. You can find a terminal
output and a backtrace in the attachments.
My system:
OS: Gentoo
uname -a: Linux gen2 5.2.16-gentoo #1 SMP Sat Sep 21 14:14:44 CEST 2019 x86_64
AMD Ryzen 7 1800X Eight-Core Processor AuthenticAMD GNU/Linux
GPU: AMD Vega 56
Window server: xorg-server-1.20.5
Window manager: i3-4.17.1
Mesa: mesa-19.2.0_rc4
LLVM: llvm-9.0.0
Download to the Gameforge Client: https://gameforge.com/en-US/download
--
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=47503
Bug ID: 47503
Summary: Problems with CreateProcess(CREATE_SUSPENDED) and
later ResumeThread
Product: Wine
Version: 4.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: ghotik2002(a)yahoo.com
Distribution: ---
I'm trying to port DxWnd ( https://sourceforge.net/p/dxwnd ) on Wine and it
runs
pretty out of the box for injection based on SetWindowsHook calls, but in many
cases it is necessary to use code injection based on thread suspension /
resume.
An injection mode uses CreateProcess(CREATE_SUSPENDED) and some later
ResumeThread
call, but the result is an alive process (I can list it with Linux ps command)
that is probably still suspended and can't take control of the desktop.
If anyone may want to replicate the test, he/she may contact me on SourceForge
DxWnd dedicated forum or write me at ghotik2002(a)yahoo.com.
--
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=45702
Bug ID: 45702
Summary: World of Final Fantasy crashes with page fault on read
access to 0x0 at address (0x1409b111f)
Product: Wine
Version: 3.14
Hardware: x86-64
URL: https://store.steampowered.com/app/552700/WORLD_OF_FIN
AL_FANTASY/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lockert.fredrick(a)gmail.com
Distribution: Debian
Created attachment 62129
--> https://bugs.winehq.org/attachment.cgi?id=62129
Backtrace
When starting World of Final Fantasy, it crashes with:
wine: Unhandled page fault on read access to 0x00000000 at address 0x1409b111f
--
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=47750
Bug ID: 47750
Summary: Linker complaining about multiple logf_finite
definitions
Product: Wine
Version: 4.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janarvottin(a)gmail.com
Distribution: ---
Created attachment 65231
--> https://bugs.winehq.org/attachment.cgi?id=65231
compilation log
When compiling 4.15 with patches from staging repository linker fails to
assemble libmvec_nonshared.a.
Same problem aried with 4.14. Partial log 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.
https://bugs.winehq.org/show_bug.cgi?id=47104
Bug ID: 47104
Summary: Cannot click anywhere on VST plugins
Product: Wine-staging
Version: 4.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paulalbertdev(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Hi !
Just wanted you to know that 10mins ago everything was working fine but then I
upgraded the staging version of wine and, since that, when I'm using windows
VSTs plugins through vst-bridge and wine, clicks on the interface are not taken
into account... So I cannot use no win VST anymore.
Gonna downgrade to dev version but got other problems (less disturbing) with
it.
Good luck for fixing the bug !
Cheers
--
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=40378
Bug ID: 40378
Summary: Monitor AOC I-menu not running
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: fatihfawaz(a)gmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Created attachment 54084
--> https://bugs.winehq.org/attachment.cgi?id=54084
Program error
i can't running application from AOC, I-menu becouse i have a bug, a bug i
attach the file. thank you...
--
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=47835
Bug ID: 47835
Summary: `-funroll-loops` breaks wine, "wine: Unhandled page
fault on write access to 0x00000000 at address ..."
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zegentzy(a)protonmail.com
Distribution: ---
As the name implies, compiling with `-funroll-loops` breaks wine. Every part of
it, from winedbg, to wine, to wineboot. Tested against both the latest wine on
git, wine 4.15, and wine 4.15. GCC 9.1.0. Arch Linux.
This is `winedbg`, for example:
```
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
00006BB2783C2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
0000634EEE5AADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
000062C321ACADB9 (thread 0010), starting debugger...
0010:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 15 84" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xea872929
```
Here is `winecfg`:
```
winecfg
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
000060CC8A44ADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
00006628B5FD2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xe16b1929
```
I'm marking this as minor, as the workaround is trivial: just don't build with
`funroll-loops`, but hopefully someone looks into it. I did some searching, and
couldn't find this already reported, but feel free to close if it's a dupe,
sorry!
--
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=46102
Bug ID: 46102
Summary: Wine cannot recognize Turkish keyboard layout
Product: Wine
Version: 3.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yurnerolinux(a)yandex.com
Distribution: ---
I noticed that in some games , both on plain Wine ( i'm using staging ) and
both on Proton.
On Fallout: New Vegas , you can't type "i" when Turkish keyboard layout
selected. Game ( or Wine probably , since game doesn't know about it ) just
shows it as " when you pressed "i" button. Same behaviour is also going on with
Skyrim.
When i set my keyboard layout to English thorugh my system , "i" starts to work
again.
Another example is Deus EX: Human Revolution - Director's Cut on Proton. I
realized i can't open up tab menu ( tab key ) when my keyboard set to Turkish.
If i set my keyboard English again , it starts to work.
My keyboard layout is Turkish Q keyboard.
--
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.