https://bugs.winehq.org/show_bug.cgi?id=55392
Bug ID: 55392
Summary: d3d9:visual - test_color_clamping() 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:visual - test_color_clamping() fails on w11pro64-amd:
visual.c:24213: Test failed: Got unexpected color 0x00000000, case 1.
See https://test.winehq.org/data/patterns.html#d3d9:visual
This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In
particular it does not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor does it 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=55391
Bug ID: 55391
Summary: d3d9:visual - test_uninitialized_varyings() 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:visual - test_uninitialized_varyings() fails on w11pro64-amd:
visual.c:23014: Test failed: Got unexpected color 0x00000000, case 3.
visual.c:23014: Test failed: Got unexpected color 0x00000000, case 6.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55390
Bug ID: 55390
Summary: d3d9:visual - test_updatetexture() 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:visual - test_updatetexture() fails on w11pro64-amd:
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
5.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
7.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
10.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
11.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
12.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
13.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
14.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
15.
visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2,
18.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55389
Bug ID: 55389
Summary: d3d9:visual - test_per_stage_constant() 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:visual - test_per_stage_constant() fails on w11pro64-amd:
visual.c:20134: Test failed: Got unexpected color 0x000000ff.
visual.c:20152: Test failed: Got unexpected color 0x000000ff.
visual.c:20170: Test failed: Got unexpected color 0x000000ff.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55387
Bug ID: 55387
Summary: d3d9:visual - test_fetch4() 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:visual - test_fetch4() fails on w11pro64-amd:
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff131313 at
(40, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff121212 at
(200, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff111111 at
(360, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff101010 at
(520, 30).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff020202 at
(40, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff2f2f2 at
(200, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff1f1f1 at
(360, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff010101 at
(520, 150).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff040404 at
(40, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff4f4f4 at
(200, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff3f3f3 at
(360, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff030303 at
(520, 270).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff232323 at
(40, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff222222 at
(200, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff212121 at
(360, 390).
visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff202020 at
(520, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 30).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 150).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 270).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(40, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(200, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(360, 390).
visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at
(520, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff131313 at
(40, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff121212 at
(200, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff111111 at
(360, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff101010 at
(520, 30).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff020202 at
(40, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff2f2f2 at
(200, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff1f1f1 at
(360, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff010101 at
(520, 150).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff040404 at
(40, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff4f4f4 at
(200, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff3f3f3 at
(360, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff030303 at
(520, 270).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff232323 at
(40, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff222222 at
(200, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff212121 at
(360, 390).
visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff202020 at
(520, 390).
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55382
Bug ID: 55382
Summary: d3d9:device - test_draw_primitive() 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:device test_draw_primitive() fails on w11pro64-amd:
device.c:3194: Test failed: DrawIndexedPrimitive failed, hr 0x80004005.
See https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x80004005 == E_FAIL
This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In
particular it does not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor does it 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=55386
Bug ID: 55386
Summary: d3d9:visual - depth_clamp_test() 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:visual - depth_clamp_test() fails on w11pro64-amd:
visual.c:14932: Test failed: color 0x0000ff00.
visual.c:14934: Test failed: color 0x0000ff00.
visual.c:14936: Test failed: color 0x0000ff00.
visual.c:14938: Test failed: color 0x0000ff00.
visual.c:14940: Test failed: color 0x0000ff00.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55384
Bug ID: 55384
Summary: d3d9:device - test_update_volumetexture() 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:device - test_update_volumetexture() fails on w11pro64-amd:
device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 6.
device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 7.
See https://test.winehq.org/data/patterns.html#d3d9:device
Where 0x80004005 == E_FAIL
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=55385
Bug ID: 55385
Summary: d3d9:device - test_surface_format_null() 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:device - test_surface_format_null() fails on w11pro64-amd:
device.c:9328: Test failed: Expected non-zero pitch, got 0.
device.c:9329: Test failed: Expected non-NULL pBits, got 0000000000000000.
See https://test.winehq.org/data/patterns.html#d3d9:device
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not 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=43859
Bug ID: 43859
Summary: Snake Pass: In-game textures appear Black, White or
Fuchsia and are extremely bright.
Product: Wine
Version: 2.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jason.bagavatsingham(a)gmail.com
Distribution: ---
Created attachment 59430
--> https://bugs.winehq.org/attachment.cgi?id=59430
Terminal Log
Found:
Upon reaching in-game, the worlds geometry is rendered correctly, but all
assets are extremely bright and appear Black, White or Fuchsia. Some colours
are visible, but overshadowed by the bloominess of the aforementioned colours.
Steps to reproduce:
# Launch Steam.
# Launch Snake Pass.
# Select New Game / Continue and select a level.
Actual Results:
In-game rendering is extremely bright and many of the textures appear
completely White, Black or colours ranging around Fuchsia.
Expected Results:
Texture appears correctly on all assets while in-game.
*Reproduction Rate:*
5/5.
Notes:
Menus / 2D assets appear correctly.
See link below for video of the issues:
https://www.youtube.com/watch?v=f5KtPyHnJyI
Environment:
Wine-Staging 2.18
--
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=42424
Bug ID: 42424
Summary: Error occurs while installing
Renesas_Flash_Programmer_Package_V30201_free.exe.
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kiwamu(a)debian.or.jp
Distribution: ---
Created attachment 57250
--> https://bugs.winehq.org/attachment.cgi?id=57250
Screen shot when the error occurs
The issue is reproduced by following:
1. Download Renesas_Flash_Programmer_Package_V30201_free.exe from following:
https://www.renesas.com/ja-jp/software/D4000308.html
2. Run the Renesas_Flash_Programmer_Package_V30201_free.exe with following:
$ wine Renesas_Flash_Programmer_Package_V30201_free.exe
3. You should see attached screen shot named "shot.png".
Could you support this issue?
Best regards,
--
Kiwamu Okabe
--
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=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=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.
http://bugs.winehq.org/show_bug.cgi?id=34529
Bug #: 34529
Summary: Game attempts to create and read from root Z:\ drive
instead of C:\ (c_drive) directory.
Product: Wine
Version: 1.7.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nemstar(a)zoho.com
Classification: Unclassified
When running the PC version of the game Shadowgun: Deadzone
(http://www.madfingergames.com/deadzone/) which is free to download and play,
I encounter a problem. The game is attempting to write to the root directory
which is the Z:\ drive by default in wine. It attempts to create a directory
named /users/<player name> with data files that pertain to the game. I know
this because I set up a test bed and used root and the directory /users/<player
name> and files within it were created successfully and the game ran as
intended.
If the Z:\ drive is removed using winecfg (as none root user) and the file is
placed or created in ~/.wine/c_drive/users/<player name>, then the game will
read the correct file on the C: drive and run as intended. If the Z:\ drive is
re-enabled, then the game will try to read from the root file system on Z: and
can not find /user/<player name> so it will not connect to a match or save
settings.
This is the case when ran as any user.
Obviously the game should not be trying to create a new directory under
C:\users in any circumstance, or as Z:\users if root is mounted as Z:\.
--
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=55355
Bug ID: 55355
Summary: My Tally prime server application crashes after some
time
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: vikasy.enjay(a)gmail.com
Distribution: ---
Following installation, the application launches when I run tallyserver.exe,
however after a while it fails and displays the message "Tallygateway server
not found" as seen below in the logs:
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"pEncodePara" in function
02d8:fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter)
"dwFlags" in function
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithHandleData
02d8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpScanMemory
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
02d8:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside
IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
01dc:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000326EBD0
02e0:err:service:process_send_command service protocol error - failed to write
pipe!
02e8:err:service:process_send_command service protocol error - failed to write
pipe!
02f0:err:service:process_send_command service protocol error - failed to write
pipe!
0308:err:service:process_send_command service protocol error - failed to write
pipe!
0310:err:service:process_send_command service protocol error - failed to write
pipe!
0318:err:service:process_send_command service protocol error - failed to write
pipe!
0320:err:service:process_send_command service protocol error - failed to write
pipe!
0328:err:service:process_send_command service protocol error - failed to write
pipe!
--
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=55368
Bug ID: 55368
Summary: NtCreateFile broken for non-ASCII with RootDirectory
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: novae.harpist06(a)icloud.com
Distribution: ---
Created attachment 74950
--> https://bugs.winehq.org/attachment.cgi?id=74950
Reproducer
Output on Windows:
00000000
Output on Wine:
C000003B
relevant logs with +file:
0114:trace:file:NtCreateFile handle=0x11fd38 access=00100001
name=L"\\??\\C:\\test" objattr=00000040 root=(nil) sec=(nil) io=0x11fd40
alloc_size=(nil) attr=00000080 sharing=00000003 disp=3 options=00204021
ea=(nil).0x00000000
0114:trace:file:nt_to_unix_file_name_no_root L"\\??\\C:\\test" ->
"/root/.wine/dosdevices/c:/test"
0114:trace:file:NtCreateFile handle=0x11fd18 access=c0110000 name=L"\0171.txt"
objattr=00000040 root=(nil) sec=(nil) io=0x11fd40 alloc_size=(nil)
attr=00000080 sharing=00000000 disp=3 options=00000020 ea=(nil).0x00000000
0114:warn:file:NtCreateFile L"\0171.txt" not found (c000003b)
--
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.