Confirming this worked on Manjaro (basically Arch) as well. So glad someone found a solution. I was pulling my hair out because I thought my Bumblebee/Optimus setup broke again.
Jesus H Christ. This is most definitely an Arch-based issue and itās upstreamās fault, as usual. Not gonna throw too much ā ā ā ā around in here, but the fine folks from the wine-gaming-nine AUR package came up with a freetype2 patch about 1-2 weeks ago to work around this, but either it got rolled back up or I lost my pacman.conf with the Ignore line in my latest /etc disaster and plain forgot. I came around here to try and make CCP my scapegoat and blame their well-intentioned-but-dogshittified ānativeā launcher and the Qtlibs abortion they came up with. But, pump my brakes, it was ā ā ā ā ā ā ā freetype2 again.
Lets do a Kickstarter for funding to buy freetype2ās patents and organization and make sure it doesnāt become another āzlibā ā ā ā ā bucket long-term disaster.
Also, I was too stupid to remember the problem lay with freetype2 despite my patching it. It went into my head that it was fixed since the 2.2.8 version had the patch and I have blind faith in wine-gaming-nine and the maintainer Treenz and if it pops for upgrade I run yaourt -Syu --no-confirm on it. This is my fault, not theirs in the least. But I mention this because this issue lead to me scrubbing my entire root partition earlier, including a full rsync restore. Thatās how dumb I am. Have so many issues with this linux EVE client I started blaming it, then my wine binaries.
SIgh. Long story longer, I will bear your children if you ask. The silliest fixes can be the most profound when youāre frustrated.
Iām surprised I didnāt find this thread earlier- I encountered this issue about a week ago, but have been busy lately and havenāt had much time to troubleshoot. EvE would launch after hitting play on the launcher and immediately crash. Once i got to the character screen but it always crashes.
So far Iāve nuked my /home/user/.eve folder and nuked wine and started from scratch and still have the same issue, but iāll be trying the Freetype fix when I get home tonight.
Strange enough, my chromebook has had no issues. Both computers run arch. I cross-referenced the error logs but didnāt find anything particularly useful other than just a generic looking report of the crash, but have seen the xwindow-type errors before. My desktop broke after an Eve update, but I think my desktop was already running newer packages than the chromebook.
Iāll let you guys know how it goes, done mobileposting for now.
Alright- so I got the launcher to work after de-selecting the dev wine builds and selecting wine-1.9.10-ccp-daily-16 instead, in-addition to downgrading freetype
not sure why I didnāt try that earlier, but iām glad iām back again.
Could you please explain a bit more how you did that ? Right after i hit the play, it crashes.
My wine version shows this:
wine --version
wine-2.19 (Staging)
Thanks.
No need to go back to 2.7, the problem was introduced when upgrading from 2.8 to 2.8.1 on Sep. 16th. Just stay on 2.8 until the launcherās wine is updated.
@Dae-Aemoz
thanks for the topic.
The fact that eve logging wrote this āXError BadWindowā message with status āinfoā I wouldnāt found it years.
I recently performed a system update and had to manually replace freetype again.
With regard to wine, at the moment under āSettingsā¦ā in the linux launcher, I have dev versions de-selected, and am using ccp-master, wine-1.9.10-ccp-daily-16.
I found this thread after I noticed this very same behavior started with Ubuntu 18.04 (bionic) yesterday.
I checked the apt logs, and sure enough the libfreetype6 packages were updated night before last (v 2.8-0.2ubuntu2 to 2.8.1-0.1ubuntu2). Guess Iāll backlevel too until theres a fix.
