http://bugs.winehq.org/show_bug.cgi?id=28394
Summary: Crash in wininet/http.ok if connection fails?
Product: Wine
Version: 1.3.28
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wininet
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Probably the test should skip if the connection fails.
We should also check to see what native InternetQueryOption does
on a failed connection (if we don't already; we do check what it does on
a closed one, at least).
Here's the log:
../../../tools/runtest -q -P wine -M wininet.dll -T ../../.. -p
wininet_test.exe.so http.c && touch http.ok
...
err:wininet:NETCON_secure_connect SSL_connect failed: 12056
wine: Unhandled page fault on read access to 0x00000008 at address
0x2abec87c5798 (thread 0037), starting debugger...
http.c:2873: Test failed: HttpSendRequest failed: 12056
Backtrace:
=>0 NETCON_GetCert+0x18(connection=(nil)) [dlls/wininet/netconnection.c:860]
1 HTTPREQ_QueryOption+0x887(hdr=0x3cab0, option=0x20, buffer=0x415e0,
size=0x22fa18, unicode=0) [dlls/wininet/http.c:2123]
2 InternetQueryOptionA+0x12b(hInternet=0x3, dwOption=0x20, lpBuffer=0x415e0,
lpdwBufferLength=0x22fa18) [dlls/wininet/internet.c:2518]
3 test_secure_connection+0x35b() [dlls/wininet/tests/http.c:2885]
NETCON_GetCert+0x18 [dlls/wininet/netconnection.c:860] in wininet: movq
0x0000000000000008(%rax),%rax
860 if (!connection->ssl_s)
--
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=16060
Summary: comctl32, gfi32, user32: tests fail, when dpi is not the
default (96)
Product: Wine
Version: 1.1.8
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine.dev(a)web.de
Created an attachment (id=17288)
--> (http://bugs.winehq.org/attachment.cgi?id=17288)
patch to dump tm.tmHeight
(As requested by Dmitry, one bug for all)
Current known tests, that fail, when dpi is not 96
(The Implementation was not checked yet):
comctrl32:monthcal
comctrl32:rebar
comctrl32:status
comctrl32:tab
comctrl32:toolbar
comctrl32:treeview
gdi:font
user32:combo
Implementations known to have bugs, where the related tests are fixed:
comctl32/header (VERT_BORDER must be 2)
Fixing the heigh of the system font will make more hidden bugs
in the Wine tree visible.
----------------------
A difference found during research is the tm.tmHeight of the system font.
(GetTextMetrics)
w98 (72, 96 dpi): 16
w98 (120): 20
w98 is broken for 144 and 192 dpi: 16
w2k (72, 96 dpi): 16
w2k (120, 144, 192 dpi): 20
Wine: always 16
The attached patch for dlls/comctrl32/tests/status.c dump
tm.tmHeight (the first value after "expect")
--
By by ... Detlef
--
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=43342
Bug ID: 43342
Summary: valgrind shows an unintialized write in
dlls/hid/tests/device.c
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
../../../tools/runtest -q -P wine -T ../../.. -M hid.dll -p hid_test.exe.so
device && touch device.ok
==10687== Syscall param writev(vector[...]) points to uninitialised byte(s)
==10687== at 0x4339023: __writev_nocancel (syscall-template.S:84)
==10687== by 0x7BC88028: send_request (server.c:228)
==10687== by 0x7BC881DB: wine_server_call (server.c:309)
==10687== by 0x7BC4A5AA: server_ioctl_file (file.c:1543)
==10687== by 0x7BC4A914: NtDeviceIoControlFile (file.c:1650)
==10687== by 0x7B44634D: DeviceIoControl (file.c:2651)
==10687== by 0x4B229B1: HidD_GetPreparsedData (hidd.c:133)
==10687== by 0x4876EBA: test_device_info (device.c:41)
==10687== by 0x48771C2: run_for_each_device (device.c:83)
==10687== by 0x4878870: func_device (device.c:386)
==10687== by 0x48796C8: run_test (test.h:603)
==10687== by 0x4879B19: main (test.h:687)
==10687== Address 0x48e7b38 is 0 bytes inside a recently re-allocated block of
size 9,296 alloc'd
==10687== at 0x7BC50812: notify_alloc (heap.c:254)
==10687== by 0x7BC54C93: RtlAllocateHeap (heap.c:1716)
==10687== by 0x4B22982: HidD_GetPreparsedData (hidd.c:131)
==10687== by 0x4876EBA: test_device_info (device.c:41)
==10687== by 0x48771C2: run_for_each_device (device.c:83)
==10687== by 0x4878870: func_device (device.c:386)
==10687== by 0x48796C8: run_test (test.h:603)
==10687== by 0x4879B19: main (test.h:687)
==10687== Uninitialised value was created by a client request
==10687== at 0x7BC505E1: mark_block_uninitialized (heap.c:208)
==10687== by 0x7BC5076D: initialize_block (heap.c:239)
==10687== by 0x7BC54CB3: RtlAllocateHeap (heap.c:1717)
==10687== by 0x4B22982: HidD_GetPreparsedData (hidd.c:131)
==10687== by 0x4876EBA: test_device_info (device.c:41)
==10687== by 0x48771C2: run_for_each_device (device.c:83)
==10687== by 0x4878870: func_device (device.c:386)
==10687== by 0x48796C8: run_test (test.h:603)
==10687== by 0x4879B19: main (test.h:687)
==10687==
--
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=44092
Bug ID: 44092
Summary: user32:sysparams test in Windows permanently
vertically shortens the test shell window
Product: Wine
Version: 2.22
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: parkerjbarker(a)yahoo.com
When I run the 64 bit winetest under Vista Ultimate 64-bit, I find that it's
the user32:sysparams test that shortens the test shell window vertically, so
that the status bar (showing how many tests have failed) is now half-showing.
The wine test shell window is not being properly restored.
--
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=47471
Bug ID: 47471
Summary: World of Warcraft, 8.2.0 New zone Nazjatar
Product: vkd3d
Version: 1.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: eaglecomputers.ok(a)gmail.com
Distribution: ---
Game freezes completely when loading into the new zone, if DX12 is being used,
but works fine if you use DX11 with DXVK.
--
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=30993
Bug #: 30993
Summary: diablo 3 d3d device error
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cleverca22(a)gmail.com
Classification: Unclassified
Created attachment 40680
--> http://bugs.winehq.org/attachment.cgi?id=40680
WINEDEBUG=trace+d3d output
when running diablo 3 on wine version d35cb8164a7635201c2ccdf73de2a78cebf6cb94
the game comes up with a fullscreen grey window (same as windows just before 3d
loads)
and gives an alert box with this message:
"graphics error
click to retry creating d3d device
click ok to retry"
clicking OK a few times changes the message slightly, to have retry/cancel,
retry just keeps retrying, cancel gives up as expected
--
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=32533
Bug #: 32533
Summary: QQDict: a button can't be displayed normally
Product: Wine
Version: 1.5.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jactry92(a)gmail.com
Classification: Unclassified
Created attachment 42928
--> http://bugs.winehq.org/attachment.cgi?id=42928
The Log
I installed QQDict in wine 1.5.20 and found that a botton in it can't be
displayed normally(as picture 1 in attachments).
I found that 'winetricks -q ie7' help a lot, just as the picture 2 in
attachments.
--
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=46592
Bug ID: 46592
Summary: Heroes III Horn of the Abyss TCP/IP issue
Product: Wine
Version: 3.0.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dplay
Assignee: wine-bugs(a)winehq.org
Reporter: kudraigor29(a)gmail.com
Distribution: ---
Created attachment 63485
--> https://bugs.winehq.org/attachment.cgi?id=63485
Debug log
TCP/IP window closes on create a host multiplayer game
--
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=24501
Summary: Games For Windows - Live: client doesn't start with
mono
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: mscoree
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
It wants .Net 3.5, but that doesn't work in wine. In mono, fails with:
** (GFWLClient.exe:8): WARNING **: The following assembly referenced from
C:\Program Files\Microsoft Games for Windows - LIVE\Client\GFWLClient.exe could
not be loaded:
Assembly: PresentationFramework (assemblyref_index=2)
Version: 3.0.0.0
Public Key: 31bf3856ad364e35
The assembly was not found in the Global Assembly Cache, a path listed in the
MONO_PATH environment variable, or in the location of the executing assembly
(C:\Program Files\Microsoft Games for Windows - LIVE\Client\).
which is WPF, and according to Mono, http://mono-project.com/WPF, they have no
plans to implement (big project, not much reward).
I'm filing a bug here mostly to collect duplicates. If a lot of duplicates show
up, perhaps Novell/Mono will change their mind...
To reproduce:
$ winetricks -q gfw mono26
$ cd .wine/drive_c/Program\ Files/Microsoft\ Games\ for\ Windows\ -\
LIVE\Client
$ wine GFWLClient.exe
--
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=46595
Bug ID: 46595
Summary: Rainbow Six Siege hangs on Uplay splash screen
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: riesi(a)opentrash.com
Distribution: ---
Created attachment 63492
--> https://bugs.winehq.org/attachment.cgi?id=63492
Log without specific debug channels
To make this clear the game is Battleye protected, but it does not even get far
enough to load Battleye. At least I could not see any traces of a Battleye dll
when looking at the logs with +loaddll.
So the problem is that the game hangs on the Uplay splash screen and doesn't do
anything else after that. There is no continuous log output or anything. It
just sits there.
The part of the log that's interesting for this issue is at the bottom of the
file after:
0034:fixme:secur32:schannel_get_mac_algid unknown algorithm 200, cipher 23
This is all the output that is generated when the game tries to start and after
its killed.
If you need any additional logging with specific WINEDEBUG channels, I am happy
to assist.
Thanks in advance,
Riesi
--
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.