https://bugs.winehq.org/show_bug.cgi?id=45542
Bug ID: 45542
Summary: regression: WeGame hangs after login.
Product: Wine
Version: 3.13
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
Distribution: ---
Created attachment 61948
--> https://bugs.winehq.org/attachment.cgi?id=61948
0001-Revert-server-Assign-a-default-label-to-all-tokens.txt
WeGame is a game platform by Tencent.
Steps to reproduce:
1. $ winetricks -q mfc42 cjkfonts
2. $ wine WeGameMiniLoader.3.6.1.5080.gw.exe
3. $ cd .wine/drive_c/Program\ Files/WeGame
4. $ WINEDLLOVERRIDES="msvcr100=n" wine tgp_daemon.exe
5. Due to bug 45540 , we can't login by an account number and password. But we
can login it by scanning its QR code. Clicking the Wechat icon and scaning the
QR code on WeChat mobile for login.
Expected: We can login and enter WeGame's game store interface.
Actually: Login successfully but it will hang.
I found that it work well on Wine-2.8 and I did a regression tests for it found
that this commit broke it:
commit a78d419420a43e1f428ac155082b87143117e381
Author: Michael Müller <michael(a)fds-team.de>
Date: Fri Jun 16 20:41:36 2017 +0200
server: Assign a default label to all tokens.
0001-Revert-server-Assign-a-default-label-to-all-tokens.txt is a patch for
reverting this commit on current Wine-3.13. And with this reverting WeGame
doesn't hang again.
--
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=53408
Bug ID: 53408
Summary: Dark Souls: Remastered has slow performance with
OpenGL renderer
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: performance, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: hverbeet(a)gmail.com
Regression SHA1: 7c844cd3c9c465bdeaf3d98d6da5f2f5e460e650
Distribution: ---
Before
0494:trace:fps:wined3d_cs_exec_present 0x103dec0 @ approx 41.94fps
After
0494:trace:fps:wined3d_cs_exec_present 0x103dec0 @ approx 12.45fps
--
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=50351
Bug ID: 50351
Summary: Slow text rendering in dofus linked to
fnIMLangFontLink2_GetCharCodePages calling
WideCharToMultiByte with CP_UNICODE
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mlang
Assignee: wine-bugs(a)winehq.org
Reporter: eijebong+wine(a)bananium.fr
Distribution: ---
Created attachment 68941
--> https://bugs.winehq.org/attachment.cgi?id=68941
Patch that fixes the text rendering slowness (probably wrong)
Dofus is very slow to render text and changing communication channels can hang
the game for a few seconds.
Profiling shows that it's spending lots of time opening files.
Tracing shows it's trying to open c_1200.nls a *lot*. That file doesn't exist.
Discussion on IRC:
```
22:45:27 nsivov> so that comes from mlang
22:45:47 gofman> mind umbstowcs and friends... what if it really ends up
searchign / opening locale file each time due to some reason (which can be
fixed)
22:46:37 gofman> or maybe it doesn't find some locale and tries again on each
character
22:48:07 zf> no such code page on Windows either
22:48:33 zf> we should probably cache failed attempts there
22:48:45 nsivov> in mlang it goes 1 char at a time * mlang_data size
22:49:30 gofman> cache missing is strange, but maybe some cached list of which
locale exist is possible
[...]
22:55:15 julliard> that's an mlang bug, CP_UNICODE is not a real codepage
22:57:01 nsivov> yes, for that particular loop it should be excluded
[...]
23:38:04 zf> just judging from the diagnosis above, it seems like
fnIMLangFontLink2_GetCharCodePages() is using CP_UNICODE in
WideCharToMultiByte() when it shouldn't
```
The attached diff fixes the slowness but is probably not correct and I
certainly don't understand enough about the cause to either write a meaningful
commit message or a 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.
http://bugs.winehq.org/show_bug.cgi?id=32643
Bug #: 32643
Summary: getsockopt() does not indicate WSAEFAULT when setting
optlen too small
Product: Wine
Version: 1.5.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: winsock
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexander255(a)lavabit.com
Classification: Unclassified
Using the attached WSA code will cause an error on Windows but NOT on WINE.
If you change "optlen" value to at least 4, the example the code will run
smoothly on both platforms.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=26822
Summary: Double click the icon in the title bar should close
the window
Product: WineHQ Bugzilla
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: florian.angermeier(a)desaster-games.com
In Windows it is the default behavior if double click the icon in the title bar
of a window it closes the window. Would it not be better if this also true in
Wine? Users of Windows software would expect such behavior.
May be this is optional and is only behaving like this if you turn of the
decoration of the windows (Which are Windows applications) through the window
manager. If the decoration through the window manager is turn off the window
have the "Windows window borders".
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45759
Bug ID: 45759
Summary: Links 2003 needs native wmvcore
Product: Wine
Version: 3.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wmp&wmvcore
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
Distribution: ---
Created attachment 62205
--> https://bugs.winehq.org/attachment.cgi?id=62205
+wmvcore log of Links 2003
Links 2003 crashes on startup with builtin wmvcore. After copying wmvcore.dll
from a prefix with wintricks wmp9 it runs fine (using winetricks wmp9
unsurprisingly also works).
I've attached a +wmvcore log from a run with builtin wmvcore.
--
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=53659
Bug ID: 53659
Summary: Beyond Good & Evil: missing images in configuration
tool
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matheus.venturini(a)acad.ufsm.br
Distribution: ---
Created attachment 73063
--> https://bugs.winehq.org/attachment.cgi?id=73063
Wine console output
Beyond Good & Evil's configuration tool (SettingsApplication.exe) doesn't show
some images that are supposed to appear when using it. This doesn't negatively
affect the use of the tool, but it ends up looking a little strange. These are
the most interesting lines on the output generated by Wine:
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x30
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
I'm using the GOG version, sadly the game doesn't have a demo for PC.
--
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=54344
Bug ID: 54344
Summary: simtower (setup.exe) says could not open the file name
"h:\wine64....."
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: elias_0000_0000(a)yahoo.com
Distribution: ---
simtower (setup.exe) says could not open the file name "h:\wine64....."
setup.exe tries to expand the files, but it says the above message.
What i must do?
I downloaded expand.exe to expand files in dosbox by hand but it takes time.
--
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=54333
Bug ID: 54333
Summary: Game "10S": crashes when starting new game
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stabilergriller(a)gmail.com
Distribution: ---
Created attachment 73899
--> https://bugs.winehq.org/attachment.cgi?id=73899
complete output of the "code error" window
A free demo of the game is provided on https://owch.itch.io/10s.
Wine boots up the main menu successfully, but crashes when actually trying to
get ingame (click the "Let's Play!" button). A "Code Error" pops up.
My stats:
OS: Arch
GPU: Intel HD Graphics 610
Driver Mesa 22.3.3
Kernel version: 6.1.5
--
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=50306
Bug ID: 50306
Summary: Riptide GP Renegade: not able to connect to online
multiplayer server (Error code 403)
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ranplayer(a)protonmail.com
Distribution: ---
Created attachment 68878
--> https://bugs.winehq.org/attachment.cgi?id=68878
Wine output
When you try to connect to the Online Multiplayer, the game shows the following
message:
"""
Connection error:
Unable to connect to the game server. Please, check you network connection and
try again. (Error code 403)
"""
I created a clean prefix and installed only the Steam client and the game. No
additional library was added. This issue happens on previous Wine versions as
well.
Game link: https://store.steampowered.com/app/443860/Riptide_GP_Renegade
Setup:
O.S: Manjaro Linux
Arch: x86_64
Kernel: 5.4.80
Desktop Environment: KDE Plasma 5.20.4
CPU: Intel Core i5-4690s
GPU: Nvidia GTX 970 4GB
--
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=54226
Bug ID: 54226
Summary: widl: implement `cstruct_out` option to generate C
bindings compatible with small struct return values
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: alvin(a)alvinhc.com
According to https://devblogs.microsoft.com/oldnewthing/20220113-00/?p=106152,
the previous C bindings are incompatible with the C++ COM ABI when the method
returns a small struct for MSVC. Their solution is to add the `/cstruct_out`
flag to the MIDL compiler
(https://learn.microsoft.com/en-us/windows/win32/midl/-cstruct-out, added in
the Win11 SDK according to comments) to generate new C bindings compatible with
the C++ COM ABI.
This is similar to the (long-standing) GCC issue with its mingw-w64 MS ABI
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64384), which has been worked
around in widl/mingw-w64 by having special wrapper functions in the C++
bindings, guarded by `WIDL_EXPLICIT_AGGREGATE_RETURNS`.
I think widl should follow suit to implement a `--cstruct_out` flag to do the
same thing for the C bindings. This does not need to be guarded by
`WIDL_EXPLICIT_AGGREGATE_RETURNS` because both GCC and MSVC has the same issue
and will require the same fix. (I do not know if we need some kind of guard for
the mingw-w64 headers to revert to the old function declarations, but given
that the old bindings are practically broken perhaps it doesn't matter.)
(I have not checked what `/cstruct_out` on MIDL actually does to the C
bindings.)
--
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=54316
Bug ID: 54316
Summary: wine staging lacks wine-staging package
(8.0~rc4~jammy-1)
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: monsterovich(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
┌(monsterovich@pc)─(pts/0)─(~)
└─(>) LANG= sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
wine-staging
The following NEW packages will be installed:
wine-staging:i386
The following packages will be upgraded:
wine-staging-amd64 wine-staging-i386:i386 winehq-staging
3 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 216 MB of archives.
After this operation, 46.1 kB of additional disk space will be used.
Do you want to continue? [Y/n]
--
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=51484
Bug ID: 51484
Summary: dmloader:loader fails randomly with a
DMUS_E_LOADER_BADPATH error
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-dmusic
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 70320
--> https://bugs.winehq.org/attachment.cgi?id=70320
Unsuccessful attempt to more reliably reproduce the failure
dmloader:loader fails randomly in test_directory():
https://test.winehq.org/data/patterns.html
loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181
loader.c:107: Test failed: SetSearchDirectory failed with 0x88781181
where 0x88781181 == DMUS_E_LOADER_BADPATH.
As of writing only w7u and cw-gtx560-1506 had failures but they are quite rare
(up to 110 runs between failures), so maybe the other platforms just got lucky.
Also once (2021-06-21) there was this set of failures:
loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181
loader.c:107: Test failed: SetSearchDirectory failed with 0
So it's as if there was a race condition causing SetSearchDirectory() to fail
until some initialization process completed. That or it's some sort of
uninitialized memory issue and the failures truly are random; or
SetSearchDirectory() checks the presence of some directory corresponding to "",
and some other process interferes with that.
The attached patch has no success reproducing this issue so maybe the cause is
external.
--
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=52107
Bug ID: 52107
Summary: %ERRORLEVEL% shall not be reset when setting an
environment variable in a batch file
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: others.meder(a)gmail.com
Distribution: ---
The fix in https://bugs.winehq.org/show_bug.cgi?id=47791 (commit
617d14bc1238b57327a8400eda1c1ab22624beb7) is incomplete; it only applies to
interactive case, and the bug is left unchanged for the batch mode case.
When a variable is successfully set, %ERRORLEVEL% is left as-is regardless of
whether the interpreter is in batch mode or not.
See also: https://ss64.com/nt/set.html
--
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=54016
Bug ID: 54016
Summary: dwmapi:dwmapi fails on Windows 10 21H2+ and 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dwmapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dwmapi:dwmapi fails on Windows 10 21H2+ and 11:
dwmapi.c:75: Test failed: Got wrong monitor refresh rate 156250/10000000.
dwmapi.c:78: Test failed: Got wrong composition rate 156250/10000000.
See https://test.winehq.org/data/patterns.html#dwmapi:dwmapi
Note that this already impacted w10pro64-rx550 when it was running 21H2.
However the TestBot's plain QXL 21H2 and 22H2 VMs are not impacted despite
having the same dwmapi.dll version. Also Windows 11's QXL test configuration is
impacted too so it's not something specific to AMD / NVIDIA GPUs.
--
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=54334
Bug ID: 54334
Summary: qasf:asfreader - test_threading(TRUE) sometimes fails
in Wine (GitLab CI)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
qasf:asfreader - test_threading(TRUE) sometimes fails in Wine:
asfreader.c:954: Test failed: blocking 1: Got hr 0x8004022a.
asfreader.c:977: Test failed: blocking 1: Wait timed out.
asfreader.c:986: Test succeeded inside todo block: blocking 1: got wrong thread
asfreader.c:998: Test failed: blocking 1: Got hr 0x1.
So far this has not shown up in the WineTest results but it has impacted the
GitLab CI results of at least two merge requests:
* MR1668
https://gitlab.winehq.org/wine/wine/-/merge_requests/1668
* MR1965
https://gitlab.winehq.org/wine/wine/-/merge_requests/1965
--
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=54159
Bug ID: 54159
Summary: kernel32:debugger - crash_and_winedbg() gets an
unexpected failure count on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:debugger - crash_and_winedbg() gets an unexpected failure count on
Windows 11 in the 'dbg,attach,process,event,detach' case:
debugger.c:610: running dbg,attach,process,event,detach...
debugger.c:621: waiting for child exit...
debugger.c:198: child: crashing...
debugger.c:659: waiting for the debugger...
debugger.c:166: debugger traces:
processing debug messages
setting event
done debugging...
debugger.c:681: Test failed: debugger reported 4 failures
See https://test.winehq.org/data/patterns.html#kernel32:debugger
While this error is systematic on Windows 11 it never happened on Windows 10
and lower... except in MR!1823 which had something very similar:
debugger.c:600: running dbg,attach,process,event,detach...
debugger.c:611: waiting for child exit...
debugger.c:198: child: crashing...
debugger.c:649: waiting for the debugger...
debugger.c:166: debugger traces:
processing debug messages
setting event
done debugging...
debugger.c:671: Test failed: debugger reported 7 failures
--
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=53863
Bug ID: 53863
Summary: Tsui no Stella = Stella of the End: doesn't launch
anymore (GL_INVALID_OPERATION)
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 73393
--> https://bugs.winehq.org/attachment.cgi?id=73393
terminal output for 7.20 and 7.19
You can get a trial copy of the game here:
https://key.visualarts.gr.jp/kinetic/stella/#download.
Random direct link:
https://sample9.dmm.co.jp/mono/pcgame/1041apc14123/1041apc14123t.zip
The game runs fine in 7.18 and 7.19 at least, but it fails to launch for me
after the update to 7.20:
0118:err:d3d:wined3d_debug_callback 0A542890: "GL_INVALID_OPERATION in
glMapBufferRange(access indicates neither read or write)".
0118:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory.
0118:err:d3d:wined3d_bo_gl_map Failed to map chunk.
0118:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo.
(Downgrading to 7.19 fixes the issue.)
[Ubuntu 18.04.6, WINE packages from the official WineHQ repo]
--
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=54330
Bug ID: 54330
Summary: Folder save-to path doesn't update if you navigate
using the "bookmarks" left sidebar; subsequently
clicking "Open" does nothing or crashes
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: NM64+bugs.winehq.org(a)PM.me
Distribution: ---
Created attachment 73893
--> https://bugs.winehq.org/attachment.cgi?id=73893
video demonstration of the full process for reproducing the issue
On software such as VirtualDub2 or RPA Explorer, when navigating the "save to"
folder location, if you instead navigate by clicking on the "bookmarks" left
sidebar, then the location entry path does not get updated.
When you do this in VirtualDub2, subsequently clicking the "Open" button does
nothing.
When you do this in RPA Explorer, subsequently clicking the "Open" button
throws up an error and crashes the program.
(also, why does the button say "Open" rather than "Save"? We're selecting the
folder to save to after all...)
See the attached video which demonstrates the issue in its entirety to the
point that you should be able to fully replicate and reproduce the issue (note
that it was performed on a live ISO of Linux Mint 21.1 Cinnamon).
And for reference, here are the URLs that were visited in the aforementioned
video:
VirtualDub2: https://sourceforge.net/projects/vdfiltermod/
RPA Explorer: https://github.com/UniverseDevel/RPA-Explorer
Example RPA file: http://katawa-shoujo.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=52177
Bug ID: 52177
Summary: Gamepad stopped working (In The Groove, Fedora 35,
wine 6.21)
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kas(a)yenya.net
Distribution: ---
After upgrade to Fedora 35 (wine-6.21-1.fc35.x86_64) from Fedora 34 I am no
longer able to play the game In The Groove (a rhythm game based on StepMania
engine): The game itself detects my gamepad both as /dev/input/eventX and
/dev/input/jsY, but when I try to configure the input, pressing buttons on the
gamepad is not recognized by the game. When I disable the /dev/input/js* (by
chmod a-rw), it can see the first four buttons out of ten, but when the button
3 is pressed, it does not see the button 0 being pressed.
When I run "jstest /dev/input/jsY", jstest recognizes all ten buttons and their
combinations. So the hardware works as expected.
What should I try in order to get the game working with my gamepad? Thanks!
--
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=54326
Bug ID: 54326
Summary: nsi:nsi - test_ndis_ifinfo() sometimes gets
out-of-order InUcastPkts bounds on Windows 10 <= 1607
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
nsi:nsi - test_ndis_ifinfo() sometimes gets out-of-order InUcastPkts bounds on
Windows 10 <= 1607:
* 2023-01-09 on w1064v1607 (64-bit)
nsi.c:344: Test failed: 1: InUcastPkts: 48607845 not in [48607847 48685030]
* 2023-01-16 on w1064v1507 (32-bit)
nsi.c:344: Test failed: 1: InUcastPkts: 19183127 not in [19183127 19183125]
See https://test.winehq.org/data/patterns.html#nsi:nsi
Only two instances so far.
--
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=28960
Bug #: 28960
Summary: Mount & Blade: WFAS configuration menu panels are
partially hidden
Product: Wine
Version: 1.3.31
Platform: x86
URL: http://www.fileplanet.com/219895/210000/fileinfo/Mount
&Blade-with-Fire-and-Sword-Demo
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pavel.ondracka(a)gmail.com
Classification: Unclassified
Regression SHA1: 3b9669017bc8425f04860f331d8a1f689c8d63e0
Created attachment 37237
--> http://bugs.winehq.org/attachment.cgi?id=37237
comparison of good and bad behavior
3b9669017bc8425f04860f331d8a1f689c8d63e0 is the first bad commit
commit 3b9669017bc8425f04860f331d8a1f689c8d63e0
Author: Huw Davies <huw(a)codeweavers.com>
Date: Wed Oct 12 11:55:13 2011 +0100
gdi32: Add the liberation fonts to the default fallback lists.
Screenshot attached, reverting mentioned commit from latest wine fixes this
issue. To reproduce: start game, select trial and click configure when launcher
menu starts.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54324
Bug ID: 54324
Summary: shell32:autocomplete - The dropdown is sometimes
unexpectedly visible in test_prefix_filtering() on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - The dropdown is sometimes unexpectedly visible in
test_prefix_filtering() on Windows:
autocomplete.c:671: Test failed: AutoComplete DropDown visible
See https://test.winehq.org/data/patterns.html#shell32:autocomplete
There have been 4 instances in the past 6 months:
* 2022-08-16 on fgtb-w10pro64 (but this one had a lot of other failures so it
may just have been a side-effect of some other issue)
* 2022-09-01 on w10pro64-hi-u8
* 2022-11-03 on w10pro64-en-AE-u8
* 2022-01-16 on w10pro64-ar
--
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.