Linux

Try clearing the browser cache folder in the launcher directory. If that doesn't help then I am a bit at a loss, the log files look good though.

Same result :( What is supposed to be displayed in that part of the launcher?

Well, the lack of a login button makes that part rather difficult ;-)

That's because of whatever wine does. My Mac Mini sits at 2.1% CPU, my Windows at 0%. This is mostly because multi-threading in Python is expensive, it performs a ton of system calls to check the GIL. Now in the case of the native windows and mac environment that is a heavy, yet insignificant prize to pay for keeping the UI responsive. However, in the case of running in Wine that seems to get worse because Wine needs to translate those Windows system calls to whatever Linux is using.

I do agree that this is not an optimal situation but it's an acceptable one for us. Rewriting the launcher in something else than Python does currently not make a lot of business sense - and trust me, I want to do it because f.e. our memory consumption is way too high and the start up times is way too slow, IMHO. This may or may not change depending on how the market evolves (and even then a native python client would perform a lot better than running inside Wine), but for now I'll have to refer you to the Wine guys and ask them what exactly it is that makes the launcher so super expensive in their environment.

Because Linux is not an officially supported platform and that makes it impossible for our team to justify spending time on it. While python runs perfectly fine on Linux, then the lesson we learned from Mac OS is that there are a lot of special cases that we need to take care of for each operating system. Starting with where the EVE client lives, where it stores its settings, etc. on to some non-standard python libraries we are using that would require porting and compilation (for which Linux distribution? Would Ubuntu be sufficient?). Since none of us on the team has EVE running under Wine (at the moment) then it is near impossible to deal with those issues.

That being said we're looking into low hanging fruit that might crop up with the launcher on Linux, but it's things like this SSL timeout (Error -7) where we simply cannot justify spending time on it when it's not straight forward.

For the immediate future your LInux based experience will still function acceptably; even though Wine fails to handle multi domain SSL connections. The EVE client can still be started, and logging in can still be accomplished there, much as you currently do.

However, since our goal is to allow alternative authentication methods, and those are designed to be implemented via web-services, at some point in the future the in-client login methods will be removed. There's no ETA for this at this time, but I am aware of the effect this would have on the EVE Linux community.

I can't promise that we will be able to fix these issues, since they appear to be fundamentally broken in Wine, but given that we're having this very discussion should point out that we're at least aware of the issues the new EVE Launcher experiences on Linux, even if we're not able to address them.

Just out of interest, what's wrong with ingame logins and why do we need a launcher at all? Every game getting a (most of the time more or less crappy and useless) web based Launcher has become a thing in the last few years and I don't really see why.

We don't really need the launcher for patching, as the game itself recognizes if it is out of date and can initiate a patcher program all by itself - we had that in the past and this still works if the game is launched via ExeFile.exe.
We also certainly don't need it for news or game related offers. We have news at the character selection screen and offers at the login screen and to be honest, if I happen to want news, I can find them myself without having them shoved in my face every gently caressing time I start Eve.

I am not saying that you should not do something because it might break wine compatibility. By all means, don't hold back features because they don't work well with some goofy 3rd party virtualisation layer for the wrong OS, the Linux community is like the Borg, we will adapt. At most we will suffer some inconveniences for a while until some dude who knows his **** comes up with a fix, we are used to that. But the thing is, from what I can see, the launcher doesn't add anything but fluff and possible error sources. Launchers are annoying and useles even when they work. Are "Never change a running system!" and "If it ain't broke, don't fix it!" not a thing anymore these days?

Dev attention to us is very, very appreciated. Even if in form of simple warnings and heads-up like this one, knowing well we're on our own when it comes to official support.

Just want to let you know that after updating to wine 1.5.30 when I close the launcher window, the console starts filling up with these error messages:

err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6da0 "rtl.c: peb_lock" wait timed out in thread 002e, blocked by 0028, retrying (60 sec)

After some time I get bash promt and ctrl+c works there too. Just wanted to warn those people thinking about upgrading wine to 1.5.30.

I think they're developing a new launcher to take advantage of SSO. And if this is the case, soon the old one will simply stop working at all - so having the option to use it would be pointless.