These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

Fedora 17 - Eve not running
Author
Previous Topic Next Topic
Calebus Phobeus
Eternal Seekers of Darkness
#1 - 2012-06-22 18:35:23 UTC
Hi there,

I am just about being a little bit puzzled. Running Eve here on a Fedora 17 system for a while now, but out of sudden it stopped to working within the last days. Everything was actually running fine before and I am not really aware of anything that changed. Typical stuff e.g. like wine was modified last time at end of may. When starting the client, I am just getting the following lines:

WINEPREFIX=~/.wine-eve wine ~/.wine-eve/drive_c/Programme/CCP/EVE/bin/ExeFile.exe
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:heap:HeapSetInformation 0x110000 0 0x33f2c8 4
Network layer using: CarbonIO
EVE Client version 7.41 build 384443 starting  20:30:22
Multi-Language System: Client using language [DE]
Starting up Trinity through _trinity_deploy.dll ...
p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:dbghelp:elf_search_auxv can't find symbol in module

System seems to freeze there and wine doesn't react anyhow nor break with anything. No crash information or anything else. I also tried going for a complete fresh wineprefix, but suprisingly for me, I am encoutering exactly the same issue. The launcher seems to run fine in both prefixes. My overrides used are as follow:
---
#msvcr100 (builtin,native)
#msvcr90 (builtin,native)
#msvcr80 (native, builtin)
---
I am actually running out of good ideas what makes Eve breaks for me. As neither a fresh install nor the existing prefix (4 month at least) aren't working and seems to be suddenly breaking, I assume that the problem is actually related somehow to the system itself. However, I am not aware of any relevant modification there. I am up for any good idea or hint for further debugging into this issue or maybe just a confirmation from another Fedora user, that he is able running eve there with the latested system updates. Maybe this helps narrowing down my issue.

Many thanks in advance!
Calebus Phobeus
Eternal Seekers of Darkness
#2 - 2012-06-22 19:23:07 UTC
Okay, I actually found a workaround for me. I missed out in the first time, that within the last days the new nvidia driver 295.59 was rolled out. After finding some debian users reporting having issues with this driver when switching in wine into fullscreen (sorry, missed the link during some reboots). Thus I gave it a try reverting back to the old driver that was released at end of may. (295.53) and actually this seems to working out. Eve was starting.

I am not 100% sure, where exactly the issue is originated (my system? Fedora? Maybe the driver and thus also affecting other distris?). Didn't find any official issues regarding this so far, so even if its working now, might be interesting for someone else as well.
xBuZZeRx
BB Deep Space Inc.
#3 - 2012-06-25 07:54:23 UTC  |  Edited by: xBuZZeRx
I got exactly the same problem here! SadSad
but i'm new to fedora and can't figure out how to downgrade.

with yum downgrade xorg-x11-drv-nvidia
I got strange dependency errors

I really need help, trying to run eve since 2 weeks now
Calebus Phobeus
Eternal Seekers of Darkness
#4 - 2012-06-25 10:18:26 UTC  |  Edited by: Calebus Phobeus
Hi there,

okay, actually good to know, that I am not completely alone with this issue. I actually think, that my initial thought about the nvidia driver might not be correct. After performing the downgrade, it was working fine for another day until it occurs again. As I didn't notice, that much others are having similar issues, I decide to reinstall the system as it was updated for multiple times. After reinstalling, everything seems to be fine - even with the latest drivers.

Yesterday, I went offline from Eve and everything was fine and now I wanted going online and having exactly the same issue. Without even restarting the system - out of nowhere - eve doesn't start anymore.

The only package that was installed yesterday, was actually some extra kernel modules I used for attaching a game pad to the system. Maybe you can check if you're having "kernel-modules-extra" installed. Additionally I am running Eve in a multihead environment using NVIDIAs prop. with separate X instances and Xinerama. Was working fine for about 6 month now before.

I am really starting to run out of ideas. So I am open for any ideas.
//edit: Just checked, removing the "kernel-modules-extra" does not fix the issue

Also adding the output of strace http://pastebin.com/yurdkPK4 Not sure, how it looks when working.
Nebu Retski
Lead Farmers
#5 - 2012-06-25 14:03:11 UTC
Calebus Phobeus wrote:
Without even restarting the system - out of nowhere - eve doesn't start anymore.


Just out of curiosity, does eve start again after you reboot your system? I occasionally have an issue with starting Eve which I have up to now only managed to fix by doing a reboot (yeah I know ******* windows style fixing). This tends to happen whenever I turn on Eve at some point, then not playing for several hours to then return to the inability to start eve before doing a reboot.
Calebus Phobeus
Eternal Seekers of Darkness
#6 - 2012-06-25 20:04:06 UTC
No, once the issue occurs, a reboot doesn't help anymore. This is especially strange, as yesterday shows, that it might work and some hours later failing. There are no obvious problems in any log so far, that might point to this issue.

What you're describing sounds more like a "BadWindow" stuff. I observed it sometimes that the client doesn't terminate correctly and causing some problems when restarting the client. It just looks like nothing is happening and in shell you're getting an error notifcation about "BadWindow". Most of the time there is a wine or eve process runnign (I am just checking for wine* and eve*). After its killed it works... or just a short CTRL+ALT+BACKSPACE.

However, my problem seems to be permanent. Everything works fine for the last 6 month and even weeks in F17 before anything wents wrong. Will now try using a different distribution to check, if I can reproduce it. Very strange issue...
Nebu Retski
Lead Farmers
#7 - 2012-06-26 09:22:08 UTC
Calebus Phobeus wrote:
No, once the issue occurs, a reboot doesn't help anymore. This is especially strange, as yesterday shows, that it might work and some hours later failing. There are no obvious problems in any log so far, that might point to this issue.


Damn that sucks.

Calebus Phobeus wrote:
What you're describing sounds more like a "BadWindow" stuff. I observed it sometimes that the client doesn't terminate correctly and causing some problems when restarting the client. It just looks like nothing is happening and in shell you're getting an error notifcation about "BadWindow". Most of the time there is a wine or eve process runnign (I am just checking for wine* and eve*). After its killed it works... or just a short CTRL+ALT+BACKSPACE.


I will check that next time I have that issue, thanks for the pointer Blink