Remove annoying fatal_error() after wineserver crash
malte at kde.org
Sun Oct 7 20:40:56 CDT 2001
not sure about the reason for that "the socket exists, but I can't connect"
message, but IMHO it's pretty annoying. I hit this fatal_exit() very often
while debugging reaktivate. And in such cases - or when starting an app from
a desktop / startmenu icon - when wine's STDERR goes to ~/.xsession-errors
instead of a shell, the user has no chance to figure why an app won't start.
Well, long story, short patch which Works for Me (TM) but I don't know if
there's anything wrong with doing this...
if the connect() to wineserver's socket fails, try to unlink it before
PGP: 1024D/D2F3C787 [C138 2121 FAF3 410A 1C2A 27CD 5431 7745 D2F3 C787]
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 552 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20011008/011b84ee/scheduler.bin
More information about the wine-patches