http://bugs.winehq.org/show_bug.cgi?id=12762
Summary: BattleLAN socket error crash Product: Wine Version: 0.9.60 Platform: PC URL: http://home.comcast.net/~sonicsmart/battlelan.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: afffect@gmail.com
BattleLAN app crashes with the following error when pressing "start":
Forwarding... socket Error:10043
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #1 from Nacho deconocio@mixmail.com 2008-05-07 06:12:53 --- Created an attachment (id=12794) --> (http://bugs.winehq.org/attachment.cgi?id=12794) trace of an execution
The trace file was too big to upload because it records all mouse movements. So I edited and pasted the parte where the error happens.
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #2 from Austin English austinenglish@gmail.com 2008-11-12 14:15:51 --- Is this still an issue in current (1.1.8 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #3 from affect afffect@gmail.com 2008-11-12 17:11:48 --- Yes, I have just tried to run it in 1.1.8 with and witout override of dplaydlls, same Socket error:10043
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #4 from affect afffect@gmail.com 2009-04-01 14:44:25 --- Still in 1.1.18
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #5 from Jeff Zaroyko jeffz@jeffz.name 2009-04-01 14:54:20 --- please attach a +winsock log
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #6 from affect afffect@gmail.com 2009-04-01 15:00:12 --- Created an attachment (id=20257) --> (http://bugs.winehq.org/attachment.cgi?id=20257) WINEDEBUG=+winsock log
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2009-04-01 15:32:23 --- (In reply to comment #5)
please attach a +winsock log
trace:winsock:WS_socket af=2 type=3 protocol=0
type 3 is SOCK_RAW, you need special permissions either using linux caps with a recent kernel or root.
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #8 from affect afffect@gmail.com 2009-04-01 15:38:12 --- So, since one shouldn't run wine as root, the only possibility is to upgrade the kernel?
http://bugs.winehq.org/show_bug.cgi?id=12762
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #9 from Jeff Zaroyko jeffz@jeffz.name 2009-04-01 15:49:02 --- Yeah, if you 'man sock_raw', you'll see:
Only processes with an effective user ID of 0 or the CAP_NET_RAW capability are allowed to open raw sockets.
To set the cap, you need to use setfcaps, but I think that's out of the scope of bugzilla. Try searching the forum or if need be seek help from your distro's support channels.
Marking invalid, not a Wine bug.
http://bugs.winehq.org/show_bug.cgi?id=12762
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Jeff Zaroyko jeffz@jeffz.name 2009-04-01 15:49:31 --- closing
http://bugs.winehq.org/show_bug.cgi?id=12762
--- Comment #11 from Austin English austinenglish@gmail.com 2009-04-01 16:18:03 --- (In reply to comment #8)
So, since one shouldn't run wine as root, the only possibility is to upgrade the kernel?
This is an example of the reason why we allow running as root, just not recommended.
You could use root here, but be aware of the potential security risk/system damage.
-
wine-bugs＠winehq.org