https://bugs.winehq.org/show_bug.cgi?id=46027
Bug ID: 46027
Summary: Some games intermittently drop controller input if >4
controllers are connected.
Product: Wine
Version: 3.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)azelphur.com
Distribution: ---
I have found that when I have more than 4 controllers connected, Sonic Mania
and Stick fight both drop controller input every few seconds. This doesn't seem
global to wine, as I don't experience the issue running Cemu, but it does seem
to effect more than one game.
If I disconnect some controllers and restart the game, everything works as it
should.
I have tested Sonic Mania on native Windows with 8 controllers connected and
the issue does not occur.
Video of issue in Stick fight: https://www.youtube.com/watch?v=ctYE1fFrBzk
Video of issue in Sonic Mania: https://www.youtube.com/watch?v=KuHTjZ0zghs
--
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=45980
Bug ID: 45980
Summary: Cisco packet tracer crashes
(secur32.LsaGetLogonSessionData is a stub)
Product: Wine
Version: 3.17
Hardware: x86
URL: https://drive.google.com/file/d/1qK79wHrDjvnWa_4JSw0AP
MIJUTsrxpLW/view
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: secur32
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Hi, a user reported trouble with this app on the forum:
https://forum.winehq.org/viewtopic.php?f=9&t=31265
It throws up an error box as can be seen in the forum-thread. I was not able to
get the backtrace from the user, for me it hangs after clicking OK.
AFAICT it only needs the LogonTime from the _SECURITY_LOGON_SESSION_DATA
structure to return something useful, then the errorwindow is gone for me, even
if still returning STATUS_NOT_IMPLEMENTED; hack below makes the app start
without errorwindow
sha1sum Packet\ Tracer\ 7.2\ for\ Windows\ 32\ bit.zip
f84e1a08b0b4f38ac977a11c7071e20c028b8d3e Packet Tracer 7.2 for Windows 32
bit.zip
diff --git a/dlls/secur32/lsa.c b/dlls/secur32/lsa.c
index 694971d714..549de73511 100644
--- a/dlls/secur32/lsa.c
+++ b/dlls/secur32/lsa.c
@@ -153,7 +153,10 @@ NTSTATUS WINAPI LsaGetLogonSessionData(PLUID LogonId,
PSECURITY_LOGON_SESSION_DATA* ppLogonSessionData)
{
FIXME("%p %p stub\n", LogonId, ppLogonSessionData);
- *ppLogonSessionData = NULL;
+ // *ppLogonSessionData = NULL;
+ SECURITY_LOGON_SESSION_DATA fake;
+ fake.LogonTime.QuadPart = 44;
+ *ppLogonSessionData = &fake;
return STATUS_NOT_IMPLEMENTED;
}
--
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=35860
Bug ID: 35860
Summary: Crysis 2 - Claims unsupported video card
Product: Wine
Version: 1.7.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jarkko_korpi(a)hotmail.com
Created attachment 47882
--> http://bugs.winehq.org/attachment.cgi?id=47882
Error while launching
Ati 7870, 14.3 beta closed source driver
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon HD 7800 Series
OpenGL core profile version string: 4.3.12798 Core Profile Context 13.35.1005
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.3.12798 Compatibility Profile Context 13.35.1005
OpenGL shading language version string: 4.30
OpenGL context flags: (none)
--
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=44072
Bug ID: 44072
Summary: Agents of Mayhem does not start
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: byi5000(a)gmail.com
Distribution: ---
Created attachment 59787
--> https://bugs.winehq.org/attachment.cgi?id=59787
wine debug log: 13.4 mb unzipped
Using wine-2.21-staging
*Could* be because of Steam CEG https://bugs.winehq.org/show_bug.cgi?id=32515
Could be something else
--
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=46009
Bug ID: 46009
Summary: "Total WAR: Attila" visual artifacts and slow
performance
Product: Wine
Version: 3.18
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
Created attachment 62581
--> https://bugs.winehq.org/attachment.cgi?id=62581
Photo
Running Total War:Attila on WineD3D has artifacts and very low framerate.
--
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=45969
Bug ID: 45969
Summary: ArcGIS Pro crashes on start
Product: Wine
Version: 3.17
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 62523
--> https://bugs.winehq.org/attachment.cgi?id=62523
console output
To reproduce:
1. Run `winetricks dotnet461`. This is a prerequisite of ArcGIS Pro.
2. Run `wine ArcGISPro_22_163783.exe`. Note that this is a 64-bit program.
3. Run `wine 'C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.exe'`.
Console output is attached.
$ sha256sum ArcGISPro_22_163783.exe
b6acceb36d51cdb1cc283478fd6170b7e51630f127ea4c841fef67d662d40f1e
--
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=43263
Bug ID: 43263
Summary: Wine cannot coexist with other ALSA programs, even
with dmix
Product: Wine
Version: 2.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: sgilles(a)math.umd.edu
Distribution: ---
Created attachment 58587
--> https://bugs.winehq.org/attachment.cgi?id=58587
.asoundrc
This machine runs Gentoo and ALSA + dmix (.asoundrc attached). I
have observed this issue with wine installed from Gentoo's repositories,
but also with wine built from git (I have observed this with commit
6ec3cd9434488ba5bc0fd271a47b7d46827477c5 for example, which is the
latest at time of writing). Every native program on this machine
(mpv, mpd, ffplay, firefox, etc) is able to play sound concurrently
with every other such program.
My options under winecfg's audio tab are different depending
on whether an ALSA-using program is currently running:
[A] (System default)
[A] Out: default
[A] Out: HDA NVidia - HDMI 3
[A] Out: HDA NVidia - HDMI 2
[A] Out: HDA NVidia - HDMI 0
[A] Out: HDA NVidia - HDMI 1
[B] Out: HDA Intel PCH-ALC887-VD Anal...
The entry marked [B] only appears if there is no such program
running. The entries marked [A] cause the "Test Sound" to be
truncated abruptly, while the entry marked [B] allows the test sound
to fully die down. Furthermore, if an entry marked [A] is selected,
running a program that produces sound will fail with lines like
err:dsound:DSOUND_ReopenDevice Initialize failed: 8889000f
in the output. I have attached a log created with wine from commit
6ec3cd9434488ba5bc0fd271a47b7d46827477c5, from a fresh, WINEARCH="win32"
wineprefix, running Warning Forever 1.08, with "(System default)"
selected (mpd is running in the background), and with
WINEDEBUG="+tid,+mmdevapi,+winmm,+driver,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio"
The expected behavior is that, since I have dmix configured, wine
should behave like other programs and play sound concurrently with
them.
I've looked around for solutions to this, and people claim that
wine has been able to coexist with other programs in the past
(hence my reporting it as a bug), but every piece of advice I
find seems to be outdated.
--
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=37950
Bug ID: 37950
Summary: Listview in uTorrent 2.4.2 (32-bit) unresponsive when
removing torrent
Product: Wine
Version: 1.7.34
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shomari.sharpe(a)gmail.com
Distribution: ---
Created attachment 50556
--> https://bugs.winehq.org/attachment.cgi?id=50556
uTorrent 3.4.2 screenshot
The following problems are noted when working with uTorrent 3.4.2 (37754)
32-bit
* clicking on a torrent (gives a textbox appearance with a cursor)
* uTorrent appears to hang when deleting a torrent
* listview redraw problems
* listview items on the left are too big
--
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=46003
Bug ID: 46003
Summary: glibc (libpthread.so.0) crashes 64-bit FPUs and
freezes screen in 32-bit applications
Product: Wine
Version: 3.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine.fixes(a)gmail.com
Distribution: ---
The 64-bit glibc libraries (specifically, libpthread.so.0 - version 2.27)
apparently use the sysenter / syscall assembly commands in order to initiate
the __libc_write() system calls, rather than the "int 0x80" command that the
32-bit libraries use.
This is fine for 64-bit Windows applications in Wine, but seems to cause a CPU
exception when running certain 32-bit applications on a 64-bit Intel CPU (such
as the Core i5), which - in turn - seems to cause stack underflow and NaN
errors on the FPU unit under certain circumstances, thus preventing the screen
from updating whenever floating point calculations are required in order to
calculate the final screen position. It can also cause unhandled exceptions and
cause the application to terminate entirely in some applications.
I am yet to identify any commercial applications which suffer from this
problem, but I have written several simple SDL and Win32 graphical programs
(compiled with version 0.9.25 of the TCC Tiny C Compiler) which demonstrate the
effects. I have provided sample code of one such application below.
This problem also appears to manifest on 64-bit Intel CPUs even when using
32-bit operating systems (such as Ubuntu 18.04-i386), but I can confirm from
testing that the 32-bit QEMU virtual machine appears to be unaffected (and,
presumably, so are 'real' 32-bit CPUs too). I have been told that 64-bit AMD
CPUs (unlike 64-bit Intel CPUs) will not trigger an error when using sysenter /
syscall in 32-bit mode, but I am yet to confirm this as I currently only have
access to Intel CPUs. Incidentally, I believe that Intel themselves advise
against sysenter / syscall in 32-bit mode.
I have been able to temporarily fix the problem from within Wine by calling the
assembly command "fninit" (which resets the FPU) at the start of the
DC_UpdateXforms() function in dlls/gdi32/dc.c, or by calling the "fninit"
command from within the application (or, in some circumstances, simply moving
the window across the screen), but obviously it would be preferable to fix the
error at source from within the glibc libraries...
I realise that this is not an error with the Wine source code itself per se,
but I have registered it here in case anybody else encounters the same problem
in future.
SAMPLE CODE
(Note: This code requires the 32-bit v.0.9.25 or v.0.9.24 version of the TCC
Tiny C Compiler, as the error does not appear to manifest on newer versions)
This simple program should display a window which changes colour between red,
green, and blue every 0.5 seconds on Windows; however, when run from within
Wine on 64-bit Intel CPUs, it appears to freeze on the first colour due to the
FPU encountering an error during the __libc_write() routine
#include <windows.h>
#include <string.h>
MSG msg;
WNDCLASS wc;
HWND hwnd;
BITMAPINFO bmp = { { sizeof(BITMAPINFOHEADER), 400, 400, 1, 32 } };
unsigned char *pBits = NULL;
HDC hdc, compatibleDC;
HBITMAP dib_section;
float f = 1.0f;
unsigned char color[3][4] = { {255, 0, 0, 255}, {0, 255, 0, 255}, {0, 0, 255,
255} };
unsigned char current_color = 0;
unsigned int i;
int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR
lpCmdLine, int nCmdShow)
{
ZeroMemory(&wc, sizeof wc);
wc.hInstance = hInstance;
wc.lpfnWndProc = (WNDPROC)DefWindowProc;
wc.lpszClassName = "Test App";
if (RegisterClass(&wc) == FALSE) return 0;
hwnd = CreateWindow("Test App", "Test App", WS_OVERLAPPEDWINDOW|WS_VISIBLE,
CW_USEDEFAULT, CW_USEDEFAULT, 400, 400, 0, 0, hInstance, 0);
hdc = GetWindowDC(hwnd);
compatibleDC = CreateCompatibleDC(hdc);
dib_section = CreateDIBSection(NULL, &bmp, DIB_RGB_COLORS, (VOID**)&pBits,
NULL, (DWORD)NULL);
SelectObject(compatibleDC, dib_section);
while(TRUE)
{
while(PeekMessage(&msg,NULL,0,0,PM_REMOVE))
{
if (msg.message == WM_QUIT) break;
TranslateMessage(&msg);
DispatchMessage(&msg);
}
/* The two float operations below will trigger the error */
f += 1.0f;
f -= 1.0f;
for(i=0; i < (400 * 400 * 4); i+=4) memcpy(&pBits[i], &color[current_color][0],
4);
/* If called here, the "fninit()" assembly routine will reset the FPU and
enable the screen to update */
// __asm__ volatile ("fninit");
BitBlt(hdc, 0, 0, 400, 400, compatibleDC, 0, 0, SRCCOPY);
current_color++;
if (current_color >= 3) current_color = 0;
Sleep(500);
}
return msg.wParam;
}
--
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=45999
Bug ID: 45999
Summary: Opening File dialog in Micrographx Windows Draw 4.0
causes Unhandled exception
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jklaas(a)appalachian.dyndns.org
Distribution: ---
Created attachment 62564
--> https://bugs.winehq.org/attachment.cgi?id=62564
Backtrace saved after application crash
Installation of Micrographx Windows Draw 4.0 works without issue.
Micrographx Windows Draw 4.0 starts without any difficulty.
I can drag a file from a file manager onto the open application to open a file.
However, if I attempt to open or save a file from any of the file management
dialogs, the application crashes with an Unhandled exception.
--
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.