https://bugs.winehq.org/show_bug.cgi?id=48545
Bug ID: 48545
Summary: SDL GameControllerAddMapping registry keys do not work
Product: Wine
Version: 5.0
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: zakk(a)rsdio.com
The registry entries to add SDL controller mappings do not work
(HKLM/CurrentControlSet/Services/WineBus/Map)
I've discovered the enumeration of the subkeys fails with ERROR_ACCESS_DENIED
If I change the RegOpenKeyExW call (line 1039 of bus_sdl.c) to use KEY_READ
instead of KEY_ENUMERATE_SUB_KEYS the enumeration succeeds and the controller
mappings are passed to SDL.
The registry keys were created with the stock wine regedit program.
I can provide a diff if really required, but I feel like this might be an issue
that needs solving somewhere else (perhaps the default permissions on registry
key creation need tweaking?)
--
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=44367
Bug ID: 44367
Summary: d2d1 FillEllipse
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: markau0(a)lycos.com
Distribution: ---
With wine set to
HKEY_CURRENT_USER Software Wine Direct3D MaxVersionGL 30002
a FillEllipse and DrawEllipse error occurs when using a windows vst (Serum)
that uses d2d1.
Without setting MaxVersionGL 30002 the display is blank (black).
Setting MaxVersionGL 30002 enables the display but also causes the FillEllipse
and DrawEllipse errors which result in drawing errors.
Video card is a Radeon HD 6670.
err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to
3.2.
err:d2d:d2d_d3d_render_target_FillEllipse Failed to create geometry, hr
0x80004001.
err:d2d:d2d_d3d_render_target_FillEllipse Failed to create geometry, hr
0x80004001.
err:d2d:d2d_d3d_render_target_DrawEllipse Failed to create geometry, hr
0x80004001.
err:d2d:d2d_d3d_render_target_FillEllipse Failed to create geometry, hr
0x80004001.
err:d2d:d2d_d3d_render_target_FillEllipse Failed to create geometry, hr
0x80004001.
etc
--
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=35782
Bug ID: 35782
Summary: Tic Tac Toe Game (vbscript) cannot be played (colon
used in for loop for placing multiple statements on
the same line)
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
similar to bug 27831
--- snip ---
$ wine iexplore file:///c:/Game.htm
...
fixme:vbscript:parse_script parser failed around L"0)=8\n\t\tfor i=1 to
8:a1(i)=i-1:next 'all lines\n\t\tc=ChooseOneCell(a1)\n\tend
if\n\tFindBestMove=c\nEnd Function\n\n\nSub PutCoin(c)\n\t'put a coin on the
cell #c for player p\n\ton error resume next\n\t'if TimeOutHldIsSet=1 then
TimeOutHldIsSet=0\n\tdim n\n\tBoardCell(c)=CurrentPlayer+1\n\tn=Coin"...
--- snip ---
Reduced case:
--- snip ---
dim a1(8)
a1(0)=8
for i=1 to 8:a1(i)=i-1:next 'all lines
--- snip ---
Regards
--
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=22749
Summary: Hard link creation from a Finddupe-generated batch
file fails (needs fsutil.exe implemented)
Product: Wine
Version: 1.1.44
Platform: x86-64
URL: http://www.sentex.net/~mwandel/finddupe/
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Finddupe has an option to generate a batch file that can be run later to create
hard links for the duplicate files it find, but these batch files don't work in
Wine:
wine: cannot find L"C:\\windows\\system32\\fsutil.exe"
The particular command it's using is this:
fsutil hardlink create "C:\test6\testfile_1.gif" "C:\test6\testfile.gif"
Copying over fsutil.exe from WinXP lets it work as expected (aside from the
native app producing corrupted output). Fsutil is documented here:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en…
A lot of these functions probably wouldn't translate to Wine well (setting NTFS
attributes, etc.) but "fsutil hardlink create" seems to do the same thing as
CreateHardLink...
--
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=50153
Bug ID: 50153
Summary: HID doesn't work on macOS Catalina and Big Sur unless
"Input Monitoring" permission is granted
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: bshanks(a)codeweavers.com
On macOS Catalina and Big Sur, if the user-level app (usually Terminal) doesn't
have permission granted for "Input Monitoring" in System Preferences ->
Security & Privacy, the IOHID support in winebus will fail with 'Couldn't open
IOHIDManager.'.
And when Wine is quitting and the driver unloads, it tries to call the
IOHIDManager that was already released, causing a crash.
IOHIDManagerOpen() is failing with kIOReturnNotPermitted because it actually
tries to "open" every matching device, which is every HID device on the system,
including the keyboard (which requires Input Monitoring permission).
(Yes, this API design is very confusing, and poorly documented).
Better is to open individual devices instead, so even if the keyboard fails to
open other devices will still work.
Also it would be ideal to not "open" a device until it's necessary, so there
won't be a permission prompt unless a Windows app actually wants to read from
the keyboard. Currently some part of Wine's HID stack requests input reports
when the device gets enumerated, triggering the permission prompt.
--
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=48396
Bug ID: 48396
Summary: 'cmd.exe /c move file1 file2' doesn't respect
non-interactive mode, causing prompt for overwrite if
destination file exists
Product: Wine
Version: 5.0-rc3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
as it says. Noticed this with some scene installers that use batch files to
uncompress and concatenate files. At one point the progress stalls and a number
of 'cmd.exe' processes just sit around, waiting for input (they are
non-interactive). Reason: Wine's cmd.exe 'move' doesn't take non-interactive
mode into account when destination file exists.
Cmd's 'copy' works.
--- snip ---
$ echo "1" > test1
$ echo "2" > test2
# fails but should work
$Â wine cmd /c move test1 test2
Overwrite Z:\home\focht\test2? (Yes|No)
--- snip ---
Setting 'COPYCMD' environment variable to '/Y' avoids the prompt, but still
doesn't overwrite the destination file with original which is another bug.
Oh boy, cmd.exe really needs some love. Still so broken after years.
Wine source:
https://source.winehq.org/git/wine.git/blob/HEAD:/programs/cmd/builtins.c#l…
--- snip ---
2959 void WCMD_move (void)
2960 {
2961 BOOL status;
2962 WIN32_FIND_DATAW fd;
2963 HANDLE hff;
2964 WCHAR input[MAX_PATH];
2965 WCHAR output[MAX_PATH];
2966 WCHAR drive[10];
2967 WCHAR dir[MAX_PATH];
2968 WCHAR fname[MAX_PATH];
2969 WCHAR ext[MAX_PATH];
...
3023 /* If destination exists, prompt unless /Y supplied */
3024 if (GetFileAttributesW(dest) != INVALID_FILE_ATTRIBUTES) {
3025 BOOL force = FALSE;
3026 WCHAR copycmd[MAXSTRING];
3027 DWORD len;
3028
3029 /* /-Y has the highest priority, then /Y and finally the COPYCMD
env. variable */
3030 if (wcsstr (quals, parmNoY))
3031 force = FALSE;
3032 else if (wcsstr (quals, parmY))
3033 force = TRUE;
3034 else {
3035 static const WCHAR copyCmdW[] =
{'C','O','P','Y','C','M','D','\0'};
3036 len = GetEnvironmentVariableW(copyCmdW, copycmd,
ARRAY_SIZE(copycmd));
3037 force = (len && len < ARRAY_SIZE(copycmd) && !lstrcmpiW(copycmd,
parmY));
3038 }
3039
3040 /* Prompt if overwriting */
3041 if (!force) {
3042 WCHAR* question;
3043
3044 /* Ask for confirmation */
3045 question = WCMD_format_string(WCMD_LoadMessage(WCMD_OVERWRITE),
dest);
3046 ok = WCMD_ask_confirm(question, FALSE, NULL);
3047 LocalFree(question);
3048
3049 /* So delete the destination prior to the move */
3050 if (ok) {
3051 if (!DeleteFileW(dest)) {
3052 WCMD_print_error ();
3053 errorlevel = 1;
3054 ok = FALSE;
3055 }
3056 }
3057 }
3058 }
...
--- snip ---
While at it you could really refactor/unify the code more. Even basic 'COPYCMD'
handling is implemented in different code style (move vs. copy):
https://source.winehq.org/git/wine.git/blob/HEAD:/programs/cmd/builtins.c#l…
$ wine --version
wine-5.0-rc3
Regards
--
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=42731
Bug ID: 42731
Summary: stack overflow when .bat script variable has more than
256 characters
Product: Wine
Version: 2.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lucianposton(a)gmail.com
Distribution: ---
Created attachment 57723
--> https://bugs.winehq.org/attachment.cgi?id=57723
bug demo
When a variable with more than (roughly) 256 characters in a .bat script is
passed as a parameter, the script fails with the following error:
err:seh:setup_exception_record stack overflow 1408 bytes in thread 0009 eip
7bc4887d esp 00240db0 stack 0x240000-0x241000-0x340000
attached .bat file that demonstrates the 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.
https://bugs.winehq.org/show_bug.cgi?id=49643
Bug ID: 49643
Summary: Calling ClipCursor too frequently can cause stack
overflow in foreground window thread.
Product: Wine
Version: 5.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: rbernon(a)codeweavers.com
Distribution: ---
Created attachment 67845
--> https://bugs.winehq.org/attachment.cgi?id=67845
Reproducing sample application
Calling ClipCursor too frequently in a non-foreground thread may cause the
foreground window thread to overflow its stack. This is happening under some
circumstances with CoD: WWII.
This is inherent to the current implementation where every ClipCursor request
from a non-foreground thread involves synchronously sending internal messages
to the foreground window thread, then to the desktop thread. Each ClipCursor
request is processed when the desktop thread is notified, growing the stack
every time, until it overflows.
The attached program can be used to easily reproduce the issue.
--
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.