EVE Online Dev Tracker

None can know the intentions of the Collective beyond the Collective themselves.
–We have reviewed the situation regarding the Inaya and Aldik systems and can report that the feature is working as intended. We acknowledge that the in-game messaging about potential states of the Invasion can be made clearer. Rest assured that the team is working on a solution.

None can know the intentions of the Collective beyond the Collective themselves.
–We have reviewed the situation regarding the Inaya and Aldik systems and can report that the feature is working as intended. We acknowledge that the in-game messaging about potential states of the Invasion can be made clearer. Rest assured that the team is working on a solution.

Hey Oz,

Let me answer your two questions.

1. To the best of my knowledge, the size of the blurb on the candidates website is automated and I don’t have any config available to modify it. As it was pointed out, there is an option to read the full post that should show everything people decided to include when submitting their application. However, this system is outdated and far from ideal. Hopefully, we can see some improvements there next time around

2. That’s correct. I went over all campaign forum posts and picked the bits to the best of my abilities to create the candidate’s card from. This was my spontaneous idea I got one afternoon when the application process was already under way to help raise awareness about the candidates within the community. Sorry to hear if you feel that I have not d...

There are many potential causes, in your case you’ll probably have to wait for the underlying issue to get fixed.

Hrm, intriguing behavior.

I do get them placed under the same process tree as you. When I close the launcher, the existance of the eve processes seems to block the launcher process from going away.

However, in my case, it seems that closing the launcher causes the eve clients to lock up a few seconds later. I guess your distro is more aggressive in murdering processes that don’t respond to a kill. It definitely didn’t do this before, but rolling back to current release causes the same behavior. Any idea when it started?

I’ve just pushed beta 1734683, containing a partial fix for the zombie process issue.

The underlying issue is that there is a background thread that can fail to initialize properly, and if it does fail to initialize it blocks termination of the entire process. That will need to be fixed by the launcher team, and affects all platforms.

However, the elg warning people were seeing was a symptom of a problem which was causing that thread to fail to initialize 100% of the time, and I have fixed that issue. You’ll get one last zombie process when the update to 1734683 happens, as the version it’s upgrading from fails to close properly. After that, for most people the zombie process issue should go away.

I also am seeing the zombie process on close issue. I’ll poke people about it.

I can’t get a repro on the “closing the launcher kills the clients” issue. Any chance Gentoo is doing something super-weird involving placing the eve instances under the process tree of the launcher, instead of launching them as independent processes?

The 150k SP item in inventory was converted to the Broken Skill Canister. So anyone who still had that will have gotten the collectible.