https://bugs.winehq.org/show_bug.cgi?id=47560
Bug ID: 47560
Summary: ws2_32:WS_getpeername behavior for on non-blocking tcp
sockets during handshake
Product: Wine
Version: 4.12.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: oysstu(a)gmail.com
Distribution: ---
Created attachment 64948
--> https://bugs.winehq.org/attachment.cgi?id=64948
Winedebug output
This bug report deals with a difference in behavior of ws2_32:getpeername. It
was discovered in the game Titan Quest Anniversary Edition when connection to a
multiplayer lobby, but can be reproduced quite easily elsewhere.
Once a non-blocking socket is connected to using ws2_32:WS_connect, and
ws2_32:getpeername is called before the TCP handshake is completed, the
resulting behavior is different on Windows and Linux.
On Linux; before the TCP handshake is completed WSAENOTCONN is returned by
ws2_32:getpeername. I.e. a socket is not connected before the handshake
succeeds, hence one cannot get the peer name
On Windows; from msdn the documentation clearly states that "The getpeername
function can be used only on a connected socket.". Apparently, once the
ws2_32:connect call has been made, it's defined as "connected" until the
handshake times out because Windows returns successfully without an error and
gives the peer info of the remote address it's trying to connect to. The error
can be reproduced by using connect to an IP/port that does not reply followed
by the call to getpeername
Now, what happens in Titan Quest is that the developers has handled the
WSAENOTCONN error by recreating the socket and doing the exact thing again
instead of waiting for the socket to connect. Obviously, that's an error on
their part, but it does work consistently on Windows.
During the handshake, the tcpi_state field of TCP_INFO will show as
TCP_SYN_SENT/TCP_SYN_RECV, which can be used to detect when this happens. I
don't know the best way to get the peer name without calling getpeername
though. I suppose it can be retrieved by re-implementing af_inet:inetgetname()
without the check for TCP_SYN_SENT, but this probably affects portability (?).
Another more portable way is to cache the address/port in wine, which obviously
only works for outgoing connections (don't see why the behavior has to change
for incoming connections anyway).
af_inet:inetgetname():
https://github.com/torvalds/linux/blob/master/net/ipv4/af_inet.c#L760
I've attached a wine debug log, which shows the connect() call followed by a
getpeername() that fails and raises an exception.
--
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=48751
Bug ID: 48751
Summary: Claybook renders black starting screen.
Product: Wine
Version: 5.4
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Created attachment 66655
--> https://bugs.winehq.org/attachment.cgi?id=66655
loaddll,d3d9,d3d,d3d11,-dxgi,-dwrite
When starting Claybook via stream, stops at a black starting screen.
015d:err:d3d:wined3d_debug_callback 0x8944540: "GL_INVALID_ENUM error
generated. Invalid buffer format.".
--
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=30808
Bug #: 30808
Summary: ConEmu: Fails to find console font
Product: Wine
Version: 1.5.5
Platform: x86
URL: http://code.google.com/p/conemu-maximus5/downloads/det
ail?name=ConEmu.120527a.7z&can=2&q=
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: techtonik(a)gmail.com
Classification: Unclassified
When started, ConEmu fails with the error:
Failed to create main font!
Requested: Lucida Console
Created: Arial
Failed to create border font!
Requested: Lucida Console
Created:
The message in stdout:
$ wine ConEmu.exe
fixme:uxtheme:BufferedPaintInit Stub ()
fixme:win:RegisterShellHookWindow (0x10072): stub
err:rebar:REBAR_WindowProc unknown msg 200b wp=00000000 lp=00495520
It looks like Wine should register default console font by default. See
upstream issue:
http://code.google.com/p/conemu-maximus5/issues/detail?id=515
--
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=48742
Bug ID: 48742
Summary: ntdll: get_modref: Conditional jump or move depends on
uninitialised value(s)
Product: Wine
Version: 5.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: jeffersoncarpenter2(a)gmail.com
Distribution: ---
Created attachment 66632
--> https://bugs.winehq.org/attachment.cgi?id=66632
Configure output.
Steps to reproduce:
* Build wine 5.3 (or commit 4dfd5f22f4). Configure output attached.
* Disable wine preloader to make valgrind a little quieter.
* Compile a test program (I used 'int main() { return 0; }') using
i686-w64-mingw32-gcc
* Run this under valgrind. Valgrind output attached.
An error near the top is
==7642== Conditional jump or move depends on uninitialised value(s)
==7642== at 0x7BC7472A: get_modref (loader.c:478)
==7642== by 0x7BC7B13A: LdrAddRefDll (loader.c:3158)
==7642== by 0x408F0237: load_driver (driver.c:176)
==7642== by 0x408F0B6A: loaderdrv_CreateWindow (driver.c:673)
==7642== by 0x40958511: WIN_CreateWindowEx (win.c:1664)
==7642== by 0x409589BF: CreateWindowExW (win.c:1798)
==7642== by 0x405FD6DF: manage_desktop (desktop.c:955)
==7642== by 0x4060327C: parse_command_line (explorer.c:764)
==7642== by 0x40603320: wWinMain (explorer.c:795)
==7642== by 0x40606A37: wmain (exe_wmain.c:55)
==7642== by 0x40606922: __wine_spec_exe_wentry (exe_wentry.c:40)
==7642== by 0x7B450045: ??? (debug.h:508)
The uninitialized value is the 'hmod' argument to get_modref.
--
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=33474
Bug #: 33474
Summary: Microsoft Project 2007 cannot load Turn On Project
Guide on View>Turn On Project Guide. Other
functionalities also not available.
Product: Wine
Version: 1.5.29
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P1
Component: jscript
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: matahari_random(a)hushmail.com
Classification: Unclassified
Created attachment 44309
--> http://bugs.winehq.org/attachment.cgi?id=44309
Desktop Screenshot showing the bug.
1. Open Microsoft Project 2007
2. Click on View > Turn On Project Guide
3. Project Guide does not load due to errors in jscript.dll and srchui.dll
Currently running WINE 1.5.29 on a 32-bit distribution of Ubuntu 12.04 LTS
logged on Unity3d Desktop.
Hardware ACER 4755G with 750GiB Hard Disk, 2GiB RAM, Intel Core i5-2430M
Processor.
This bug also affected previous WINE Versions.
--
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=48481
Bug ID: 48481
Summary: Settings for Templates and Downloads locations aren't
exposed in winecfg
Product: Wine
Version: 5.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Currently winecfg has settings for symlinking or not for a bunch of standard
locations, but Templates and Downloads aren't exposed so they are always
symlinked.
Please add them to the current list.
--
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=48719
Bug ID: 48719
Summary: wow bat launcher doesn't work
Product: Wine
Version: 3.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: py_lrr(a)hotmail.fr
Distribution: ---
Created attachment 66592
--> https://bugs.winehq.org/attachment.cgi?id=66592
Console backtrace
Hi,
Trying to launch a wow BfA application with a bat file, I got an error (see the
console log as attachment).
I guess the important is the UnknowError block.
The .bat only contains : "Arctium.data" --custom Wow.exe
Arctium.data seems to be compiled and Wow is the standard wow application.
I tried to get some Arctium source but it is hard, I hope there is enough data
without it.
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.
http://bugs.winehq.org/show_bug.cgi?id=14949
Summary: ABBYY FineReader Pro 7.0 Scrolling Problem
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Windows 2000
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wbrells(a)yahoo.com
With WINE under UBUNTU 8.04 horizontal scrolling does not work in the right
hand (text editing) window of FineReader 7.0 Pro. Vertical scrolling works fine
as does horizontal scrolling in all other windows. The only workaround is to
Zoom out and/or enlarge the size of the "problem" window so all text is
visible.
--
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=48689
Bug ID: 48689
Summary: Wine 5.3 on Mac OS X 10.13.6 High Sierra: Segmentation
fault
Product: Wine
Version: 5.3
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tobbi.bugs(a)googlemail.com
Since updating to Wine 5.3, I keep getting a segmentation fault when starting
any kind of program. The issue is reproducible with a new wine prefix as well
(so my prefix is not the culprit).
$ wine --version
wine-5.3
My lldb doesn't really give any verbose information.
$ lldb wine explorer
(lldb) target create "wine"
Current executable set to 'wine' (i386).
(lldb) settings set -- target.run-args "explorer"
(lldb) r
Process 15164 launched: '/Applications/Wine
Devel.app/Contents/Resources/wine/bin/wine' (i386)
Process 15164 stopped
* thread #2, stop reason = exec
frame #0: 0x7c405230 dyld`_dyld_start
dyld`_dyld_start:
-> 0x7c405230 <+0>: popl %edx
0x7c405231 <+1>: pushl $0x0
0x7c405233 <+3>: movl %esp, %ebp
0x7c405235 <+5>: andl $-0x10, %esp
Target 0: (wine-preloader) stopped.
(lldb) bt
* thread #2, stop reason = exec
* frame #0: 0x7c405230 dyld`_dyld_start
--
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.