socksify fails running wine

[Daniel Bason]

I am using Ubuntu 10.04 LTS, dante-client 1.1.19, and wine 1.2 rc4.
When using wine to play Aion, the game hangs when it tries to make a connection through my proxy. After authentication the game just sits there waiting as if it has no response from the game server. I have an ssh tunnel set up to use 127.0.0.1:1080

My /etc/dante.conf file contains the following:
route {
 from: 0.0.0.0/0 to: 0.0.0.0/0 port=7777 via: 127.0.0.1 port = 1080
 protocol: tcp udp # server supports tcp and udp.
 proxyprotocol: socks_v5
}

the command I use to run the application is:
socksify wine "C:\Program Files\NCSoft\Aion\bin32\aion.bin" -noauthgg -ip:206.127.153.247 -port:2106 -cc:1 -lang:enu -noweb

(206.127.153.247:2106 is the authentication server for Aion, an mmo. Once authenticated it connects to the game server on 7777 hence the entry in dante.conf.

The output from socksify, once I have successfully authenticated is:
Jun 25 19:07:42 (1277449662) wine[1694]: socks_nbconnectroute(): sigchld sa_flags not handled currently,
contact Inferno Nettverk A/S for more information
Jun 25 19:07:42 (1277449662) wine[1694]: socketoptdup(): setsockopt(0, 32): Invalid argument (errno = 22)
Jun 25 19:07:42 (1277449662) wine[1694]: socketoptdup(): setsockopt(0, 33): Invalid argument (errno = 22)
Jun 25 19:07:42 (1277449662) wine[1694]: socketoptdup(): setsockopt(0, 32): Invalid argument (errno = 22)
Jun 25 19:07:42 (1277449662) wine[1694]: socketoptdup(): setsockopt(0, 33): Invalid argument (errno = 22)
Jun 25 19:07:42 (1277449662) wine[1767]: an internal error was detected at ../lib/connectchild.c:447
value = -1, version = $Id: connectchild.c,v 1.119 2005/12/24 16:44:57 michaels Exp $: Bad file descriptor (errno = 9)
wine client error:9: write: Bad file descriptor

If you need any further information, or I'm doing it wrong please let me know. I'm not sure if this is a bug in dante-client or wine - I have noted http://bugs.winehq.org/show_bug.cgi?id=8686 but am not sure if this is the same thing.

[Mercury (warp-spam-launchpad)]

Alright, so I have bisected down my crash to bcd5023c961a44c7149936553b6929b2b233dd27, which alters the lid detection logic.

Reverting this change in 2.6.39 results in a kernel that is vaguely usable, however there is no output to the laptop's display.

Closing the lid works, it redetects displays and we are still good.

Reopening the lid causes the laptop to lock solid, exactly as it was on starting X.

I am now attempting to bisect where eDP handling for my laptop broke, joy.

On the bright side, bcd5023c961a44c7149936553b6929b2b233dd27 is confirmed to impact my system as well. (HP 8440p)

Zephaniah E. Loss-Cutler-Hull.

[Mercury (warp-spam-launchpad)]

... If someone could please tell me how to delete or modify comments here, my last comment was on the wrong bug entirely, my apologies.