https://bugs.winehq.org/show_bug.cgi?id=47588
Bug ID: 47588
Summary: AmiKitXE crashes on PlayOnLinux 4.3 with Wine
3.21-staging
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mortenweb43(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64993
--> https://bugs.winehq.org/attachment.cgi?id=64993
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
Please help make it work again :-)
Error log is attached.
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=55380
Bug ID: 55380
Summary: d3d9:d3d9ex - test_swapchain_parameters() fails on
w11pro64-amd
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:d3d9ex - test_swapchain_parameters() fails on w11pro64-amd:
d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 23.
d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 23.
d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 25.
d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 25.
See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex
Where 0x80004005 == E_FAIL
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they don't happen on fgtb-w10pro64-rx550 the only other test machine
to have an AMD GPU, nor do they happen on the other Windows 11 test machines
(w11pro64 and w11pro64-nv).
--
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=41395
Bug ID: 41395
Summary: CreateFile returns a wrong LastError Code when you
pass an invalid path
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: Christoph(a)ApiViewer.de
Distribution: ---
CreateFile returns a wrong LastError Code when you pass an invalid path.
Testcase:
CreateFileA("C:C:\\Windows", GENERIC_READ, FILE_SHARE_READ,
NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
todo_wine ok( GetLastError() == ERROR_INVALID_NAME, "Wrong LastError %d,
expected ERROR_INVALID_NAME\n", GetLastError() );
Which also means the code in cryptnet_main:1025 to line 1048 must be wrong.
--
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=55379
Bug ID: 55379
Summary: kernel32:loader sometimes gets a bad thread count on
Windows 10 in phase 0/1
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:loader sometimes gets a bad thread count on Windows 10 in phase 0/1.
So far there are only two instances, both in the 64-bit tests:
* 2023-07-31 w1064-adm 64-bit tests
loader.c:2875: phase 1: writing 00007FF633B64570 at 0x202
loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2399: 1eb0: mutex_thread_proc: starting
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2954: Test failed: attached thread count should be 2
* 2023-06-07 fgtb-w10pro64 64-bit tests
loader.c:2875: phase 0: writing 000000000048FED0 at 0x202
loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2399: 1414: mutex_thread_proc: starting
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000
loader.c:2954: Test failed: attached thread count should be 2
See https://test.winehq.org/data/patterns.html#kernel32:loader
--
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=55378
Bug ID: 55378
Summary: Can't get resolutions list for scanner
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ilya.docin(a)contentai.ru
Distribution: ---
Created attachment 74954
--> https://bugs.winehq.org/attachment.cgi?id=74954
Twister Analysis of HP LaserJet MFP M426fdn
OS: Ubuntu 20.04.1
Component: sane.ds
I use Twister utility to analyze some scanners on Wine. Many scanners return
resolutions in a form of array. E.g., HP LaserJet MFP M426fdn. Twister
indicates that getting resolutions for such scanners is unsupported.
Screenshot is 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=55375
Bug ID: 55375
Summary: Can't set color mode for scanner
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: ilya.docin(a)contentai.ru
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 74952
--> https://bugs.winehq.org/attachment.cgi?id=74952
Twister analyze for HP LaserJet Pro M428-M429f
OS: Ubuntu 20.04.1
Wine version: wine-8.0.2
Component: sane.ds
I use Twister utility to analyze some scanners on Wine. When it tries to set
color mode to any scanner, both report and Wine log says, that value is not
set.
I attached screenshot with report.
--
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=55376
Bug ID: 55376
Summary: [USER32/NTUSER] Keyboard app accents doesn't change
the keys correctly.
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: julenuri(a)hotmail.com
Distribution: ---
Wine version: 8.13
Environment: Debian 11
Software tested: Accents 1.0 from this web:
https://www.dcmembers.com/skrommel/download/accents/#
Steps to reproduce: The functionality is simple. After 3 or more keyboard
inputs in the letters A, E, I, O, U or Y, you will have accent mark.
1. start the software accents
2. start wine notepad or whatever notepad you want.
3. input 3 "a"
There is a failure somewhere into key hooking process: WH_KEYBOARD_LL,
WM_USER+(number), DWL_MSGRESULT, PM_NOREMOVE, VK_LSHIFT [have a bad value
(-32768)], GetAsyncKeyState, CharLowerA, SetWindowsHookExA, CallNextHookEx,
VkKeyScanExA, MapVirtualKeyA. I'm not sure where because I'm not developer and
I have zero time to check where is exactly the failure.
Expected behavior: It should write å.
Issue: But in fact, it only deletes the input.
Video of the issue: https://youtu.be/B56TUdg3zQ8
Video of example of no issue:
https://www.dcmembers.com/skrommel/wp-content/uploads/sites/2/2017/10/Accen…
We detected the same behaviour in ReactOS too long time ago, but I guess no-one
tested in Wine before: https://jira.reactos.org/browse/CORE-5627
--
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=52296
Bug ID: 52296
Summary: UltraVNC 1.3.4.0 and later hangs after pressing
Connect.
Product: Wine
Version: 7.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Starting vncviewer with no parameters shows the connection window.
After specifiying a UltraVNC server (1.3.6.0) and pressing "Connect"
the connection window closes and nothing more happens.
This is observable with versions 1.3.4.0, 1.3.4.1, 1.3.4.2, 1.3.6.0.
In previous version 1.3.2a after pressing "Connect"
a connection status window and another window to enter the password appears.
--
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=55332
Bug ID: 55332
Summary: 00d8:fixme:setupapi:CM_Get_Device_Interface_List_SizeW
000000000011F5B8 0000000180045FD8 (null) 0x00000000:
stub
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 74926
--> https://bugs.winehq.org/attachment.cgi?id=74926
log about trying to run "wine usbip.exe attach ..."
Trying to run
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
fails with the attached error. The same command on linux
usbip attach -r <USBIB_SERVER> -b 1-1.2.4.2
is working fine. In order to reproduce this, you need
- an usbip server running some linux with hostname or IP-ddress <USBIP-SERVER>,
with some usb-device attached,
- start the usbip deamon with this command:
usbipd -D
- check the busid of the usb device with
usbip list --local
- bind the usb device,
usbip bind --busid=1-1.2.4.2
This provides remote access (port 3240 by default).
Next you install usbip-win2 from
https://github.com/vadimgrn/usbip-win2/releases
in wine, and try to connect to the usbip server with
usbip list --remote=<USBIB_SERVER>
This should show the exported USB devices.
However, the command
wine usbip.exe attach -r <USBIB_SERVER> -b 1-1.2.4.2
will fail with the attached error.
--
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.