https://bugs.winehq.org/show_bug.cgi?id=49484
Bug ID: 49484
Summary: test_query_process_image_info() test is broken on a
not PE build
Product: Wine
Version: 5.11
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
Distribution: ---
Steps to reproduce:
cd wine/dlls/ntdll/tests
make info.ok
info.c:1843: Test failed: got c0000019
info.c:1846: Test failed: wrong major version cccc/4
info.c:1848: Test failed: wrong minor version cccc/0
In fact it never worked from the point when it was added:
commit 54a7e592e44622ecd61160498fb5148a46b2e8db
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue May 26 13:23:21 2020 +0200
ntdll: Implement ProcessImageInformation class in
NtQueryInformationProcess().
It looks like in a not PE build process->views on the server side is always
empty, and as a result mapping.c,find_mapped_view() returns NOT_MAPPED_VIEW.
There's no a single DLL in the process->views, and that's a real regression,
probably caused by the movement to PE/ntdll unixlib introduction.
--
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=48790
Bug ID: 48790
Summary: mfplat:mfplat crashes on Windows 7
Product: Wine
Version: 5.2
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression, source, testcase
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
CC: dereklesho52(a)Gmail.com
Regression SHA1: b7047b5ae9fc84a6414db9bb80c4264b1550c7a0
Distribution: ---
mfplat.c:1444: Tests skipped: Cannot retrieve IMFAttributes interface from
IMFByteStream
mfplat.c:527: this is the last test seen before the exception
03f8:mfplat: unhandled exception c0000005 at 70BF7243
--
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=17848
Summary: Windows Print Preview: Lines drawn have incorrect width
Product: Wine
Version: 1.1.17
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: olsentest(a)comcast.net
In Windows print preview, drawing commands embedded
between BeginPath and EndPath have line widths that
are way too wide. It appears that the same width
(in pixels) is used in the print preview as was used
for the main application window. Also, if you use
the print preview zoom button, the line width remains
the same, suggesting that it is not being adjusted
for the changes in scale.
If drawing commands are not embedded between BeginPath
and EndPath, then the print preview appears to work
correctly.
I am attaching a screen capture of the main window and
the print preview window. Also, I am attaching a
simple Windows program that can be used for debug
purposes. Also attached is a code snippet from the
Windows program.
--
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=30469
Bug #: 30469
Summary: crash in segflex
Product: Wine
Version: 1.5.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: daduck10(a)gmail.com
Classification: Unclassified
Created attachment 39845
--> http://bugs.winehq.org/attachment.cgi?id=39845
crash file and debug mode files
The program segflex is crashing when I initialize it. I installed framework,
because it needs to run.
--
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=43408
Bug ID: 43408
Summary: Running Quest with Dotnet 4.0 crashes
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: anthonysharkboy99(a)yahoo.com
Distribution: ---
Created attachment 58755
--> https://bugs.winehq.org/attachment.cgi?id=58755
Quest Error Log
I know that dotnet 4.0 doesn't fully work as of yet. However I wanted to submit
a report because it might improve the situation.
It should be noted that I am running the staging version. However I haven't
tested the issue in normal Wine. Therefore I haven't submitted it as a staging
specific issue yet.
So after creating a 32bit prefix and installing Dotnet 4.0 by using Winetricks,
Quest will outright crash. It will refuse to boot unless you run it from
terminal. Once you run it from terminal, Quest will spit out an error report. I
have posted the crash log and attached it.
Quest can be downloaded at the following site should you want to recreate the
issue.
http://textadventures.co.uk/quest/desktop
--
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=39407
Bug ID: 39407
Summary: LabVIEW 2014: Crash when run the program.
Product: Wine
Version: 1.7.52
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zat_xorg(a)hotmail.com
Distribution: ---
Created attachment 52523
--> https://bugs.winehq.org/attachment.cgi?id=52523
Backtrace file when I run the program
LabVIEW 2014: Crash When run the program (wine LabVIEW.exe)
Note that although the installer could complete successfully, it show popup's
error during the installation process.
--
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=48714
Bug ID: 48714
Summary: mass effect spits error when using mouse fix
Product: Wine
Version: 5.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maniikarabera(a)protonmail.ch
Distribution: ---
Created attachment 66586
--> https://bugs.winehq.org/attachment.cgi?id=66586
log with dinput8=n
mouse fix from
https://community.pcgamingwiki.com/files/file/841-mass-effect-mouse-fix/
--
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=38501
Bug ID: 38501
Summary: GetClipboardData(CF_UNICODETEXT) - return ANSI
Product: Wine
Version: 1.7.39
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rozhuk.im(a)gmail.com
GetClipboardData(CF_UNICODETEXT) return non unicode text after CTRL+C in ms
richedit control.
--
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=47368
Bug ID: 47368
Summary: TAPI 3.x COM browser 'Tb3x.exe' from Windows 10 SDK
(10.0.17763.x) wants 'tapi3.dll' COM server/typelib
Product: Wine
Version: 4.10
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: tapi32
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
as it says. Tb3x is a TAPI 3.x test tool/suite to execute all TAPI3 methods
available via ITxxx interfaces and receive TAPI3 events. The COM-based TAPI was
introduced as 3.x with Windows XP. Wine doesn't provide it at all.
I didn't found any other real world applications using COM-based TAPI yet, so
consider it a low priority one.
--- snip ---
$ pwd
/home/focht/wine-apps/wineprefix64-win10sdk/drive_c/Program Files (x86)/Windows
Kits/10/bin/10.0.17763.0/x86
$ WINEDEBUG=+seh,+relay,+ole,+variant wine ./TB3x.exe >>log.txt 2>&1
...
0035:Ret ole32.CoInitializeEx() retval=00000000 ret=0041363d
0035:Call oleaut32.LoadTypeLibEx(0015fc84 L"tapi3.dll",00000002,0034ee90)
ret=00413045
...
0035:trace:ole:LoadTypeLibEx (L"tapi3.dll",2,0x34ee90)
0035:Call KERNEL32.SearchPathW(00000000,0015fc84
L"tapi3.dll",00000000,00000105,0034ebb4,00000000) ret=7e23efff
0035:Ret KERNEL32.SearchPathW() retval=00000000 ret=7e23efff
0035:Call KERNEL32.GetSystemDirectoryW(0034ebb4,00000105) ret=7e23fa43
0035:Ret KERNEL32.GetSystemDirectoryW() retval=00000013 ret=7e23fa43
0035:Call KERNEL32.CreateFileW(0034ebb4
L"C:\\windows\\system32\\tapi3.dll",80000000,00000000,00000000,00000003,00000080,00000000)
ret=7e23f02e
0035:Ret KERNEL32.CreateFileW() retval=ffffffff ret=7e23f02e
...
0035:Call KERNEL32.LoadLibraryExW(0034ebb4
L"C:\\windows\\system32\\tapi3.dll",00000000,0000000b) ret=7e23f140
0035:Ret KERNEL32.LoadLibraryExW() retval=00000000 ret=7e23f140
...
0035:Call KERNEL32.LZOpenFileW(0034ebb4
L"C:\\windows\\system32\\tapi3.dll",0034eb2c,00000000) ret=7e23f3d6
0035:Ret KERNEL32.LZOpenFileW() retval=ffffffff ret=7e23f3d6
...
0035:Call KERNEL32.CreateFileW(0034ebb4
L"C:\\windows\\system32\\tapi3.dll",80000000,00000001,00000000,00000003,00000000,00000000)
ret=7e23f460
0035:Ret KERNEL32.CreateFileW() retval=ffffffff ret=7e23f460
...
0035:err:ole:TLB_ReadTypeLib Loading of typelib L"tapi3.dll" failed with error
2
0035:trace:ole:LoadTypeLibEx returns 80029c4a
0035:Ret oleaut32.LoadTypeLibEx() retval=80029c4a ret=00413045
0035:Call user32.MessageBoxW(00000000,00401eb0 L" Sorry!\n Load TLB
FAILED!!!\n(Maybe DLL name is wrong?)",00000000,00000010) ret=00413329
...
--- snip ---
https://docs.microsoft.com/en-us/windows/desktop/tapi/tapi-applications
$ sha1sum 17763.1.180914-1434.rs5_release_WindowsSDK.iso
e702b5e5f2597d01eaee1eb1be7a34b0da0b6211
17763.1.180914-1434.rs5_release_WindowsSDK.iso
$ du -sh 17763.1.180914-1434.rs5_release_WindowsSDK.iso
815M 17763.1.180914-1434.rs5_release_WindowsSDK.iso
$ wine --version
wine-4.10-154-gc674ceefe1
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.