Linux

Don't worry about the double slash, that should not pose a problem. Just making a guess, did you at some point try running this with sudo permissions?

What's the output of the following command:

stat -c "%U %G" ~/.eve/wineenv 

Not that I think it matters much, but what does the sudo do in that launch command?

When you are in your own directory normally there should be no need for elevated root commands.
Only specific commands need sudo, mostly related to system files, as it can harm your system badly.
For users sudo is normally not needed.

in a terminal you can see who owns the .eve directory, type ls -la and it will show the owner.
That directory and subdirectories and all the files should be owned by you and not root.

EVE should be installed as a user NEVER with sudo.

The proper command to start EVE is just
~/Downloads/evelauncher/evelauncher.sh or
Downloads/evelauncher/evelauncher.sh

If you have to you use sudo there is something seriously wrong with your setup.

As for your videocard, if you disable the onboard graphics in bios does buntu boot with the DE and bytheway which DE
do you use?

To make my life a bit easier I made a directory Games, installed various other games too, and unpacked the launcher there
with just tar -xf evelauncher-xxxxxxx.tar.gz, all as user NOT with sudo as that will unpack everything as root.
Did the install, while in that Games directory, with just evelauncher/evelauncher.sh

In any case, I'd recommend you stop using sudo for games and applications. It tends to break things and it's a risk to your system security. Delete ~/.eve and the launcher, download the launcher again and just start it either through

sh evelauncher.sh

or just

./evelauncher.sh

without using sudo or even su.

Thank you, Roesjka and Neuntausend, for your help. Responses:

1) Regarding root-owned objects. I used ls -la to survey /.eve and /evelaucher, listing items marked as root:
in /.eve,
updater
in /Downloads/evelauncher,
drwxr-xr-x 2 root root 4096 Dec 13 00:24 errorpage
-rwxr-xr-x 1 root root 1221980 Dec 13 00:24 evelauncher
-r-xr-xr-x 1 root root 312 Dec 13 00:24 evelauncher.sh
a few dozen links having names in the form [lib*.so*]

Thinking I should LEARN MORE LINUX, delete eve, and reinstall fresh. (Maybe not in that order...)

2) Regarding use of sudo:
xxx@yyyyy:~/Downloads/evelauncher$ evelauncher.sh
evelauncher.sh: command not found

This happens frequently. Looking for ways to do things, at sites like stackexchange, askubuntu, etc., I'd copy suggestions,
and use of sudo seemed common. Anyway, both

sh evelauncher.sh
and
bash -x ~/Downloads/evelauncher/evelauncher.sh 2>&1 | tee CKlogN.file

work! I didn't know about sh, bash didn't seem to work before this last launcher update.

3) As you both have been really helpful, kind of reluctant to get into the video card problem, but anyway...
-- I plugged my new EVGA GeForce 1050 Ti in the topmost PCIe slot in my tower.

-- I learned that the card isn't supported yet in 16.04, but I could get a PPA for nvidia-375, just out of beta I think, at
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

-- I did things like
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update

sudo apt-get install nvidia-375

In the Other Software tab of Software & Updates, added
deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial main
deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial main

-- So, in the Additional Drivers tab, there's a listing for Nvidia,
"Using NVIDIA binary driver - version 375.26 from nvidia-375 (open source)"

-- I did a couple of other things, such as installing mesa-utils. Details are, sadly, fuzzy at the moment. This was about a fortnight ago. I rebooted, and one of my two displays lit up, asking for my crypt password; I typed it in, but the text appeared not in the text field but in the upper-left corner of the screen, and the login didn't progress to asking for my account password.

-- Anyway, the BIOS graphics hardward option had been set to Auto. I set it to the graphics card in the PCIe slot, no joy. Set it to the on-board hardware, and looked for diagnostics procedures, such as

$lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c82 (rev a1)

$ find /dev -group video
/dev/fb0
/dev/dri/card0
/dev/dri/renderD128
/dev/dri/controlD64

$ glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center

$ cat /proc/driver/nvidia/version
cat: /proc/driver/nvidia/version: No such file or directory

$ apt-cache search nvidia | grep -P '^nvidia-[0-9]+\s'
nvidia-331 - Transitional package for nvidia-331
nvidia-346 - Transitional package for nvidia-346
nvidia-352 - Transitional package for nvidia-361
nvidia-304 - NVIDIA legacy binary driver - version 304.132
nvidia-340 - NVIDIA binary driver - version 340.98
nvidia-361 - Transitional package for nvidia-367
nvidia-367 - NVIDIA binary driver - version 367.57
nvidia-355 - NVIDIA binary driver - version 355.11
nvidia-358 - NVIDIA binary driver - version 358.16
nvidia-364 - NVIDIA binary driver - version 364.19
nvidia-370 - NVIDIA binary driver - version 370.28
nvidia-375 - NVIDIA binary driver - version 375.26 <<<< this is the one the 1050 card needs.

$ sudo apt-get install nvidia-375
[sudo] password for xxxx:
Reading package lists... Done
Building dependency tree
Reading state information... Done
nvidia-375 is already the newest version (375.26-0ubuntu0~gpu16.04.1). <<<<<<<
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-47 linux-headers-4.4.0-47-generic linux-image-4.4.0-47-generic linux-image-extra-4.4.0-47-generic
linux-signed-image-4.4.0-47-generic ubuntu-core-launcher
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ nvidia-settings
ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
ERROR: Error querying connected displays on GPU 0 (Missing Extension).

** Message: PRIME: No offloading required. Abort
** Message: PRIME: is it supported? no

ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at
/usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot
be prepopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions.

(So the NVIDIA X-Server Settings dialog came up, but the card wasn't listed.)

$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver.
Make sure that the latest NVIDIA driver is installed and running.

So. I apologize for the probably hopelessly muddled reporting here. Would be grateful if y'all saw something like "OMG, you just have to flip this little switch over here, you twit!"

evelauncher.sh

that wouldn't work. evelauncher.sh is basically just a text file you need to tell the system what to do with. It's not an executable binary, but a script (a script written for the shell, or sh in short, hence the file name extension ".sh"). If you just type in the file name of that script, it doesn't know what to do with that.

You'd either need to do

/some/folder/evelauncher.sh

or, if you are in /some/folder/ already

./evelauncher.sh

Why exactly it works if you just put a path in front of it is beyond me, but I know it does, and that's good enough for the time being.

Unlike evelauncher.sh,

sh

or

bash

are binaries, and their location is most certainly in your systems PATH variable, so the system knows what it's supposed to do with them (execute). If you call

sh evelauncher.sh

or

bash evelauncher.sh

then you are telling the system to start sh or bash, and you are telling sh or bash in turn to parse "evelauncher.sh" by specifying it as a parameter, in the same sense you could also do

nano evelauncher.sh

That would tell the system to start nano, and it would tell nano to load up evelauncher.sh

On the topic of your graphics drivers - this may be a question better suited for the ubuntu forums. I am not an ubuntu person myself, and all its colourful and oh so convenient clicky interfaces are basically just voodoo to me, but maybe I can figure something out.

First, try this:

dpkg-query -l 'nvidia*'

This should list all packages you currently have installed that are called nvidia-something. Then run

sudo apt-get purge nvidia-something nvidia-settings-something nvidia-whatever nvidia-foo nvidia-bar

for every nvidia package you have on your system, which will uninstall these packages and remove their configuration as well, followed by

sudo apt-get autoremove

which will remove all dependencies that have automatically been installed at some point.

For good measure, I'd also throw in a

sudo apt-get autoclean

which will delete the apt cache. This cache contains the files apt downloads before installing anything. If you clean it, apt will have to download a fresh version if you install the drivers again.

Then do

sudo apt-get install nvidia-375

to install the driver, and while a reboot should not be strictly necessary, reboot.

you can check afterwards which driver is in use with

lspci -k

Thanks Neuntausend and Roesjka! Felt like an urchin on a wintry night, nose pressed to the window, looking in...
Best regards,
Christoph

Does anyone know what to do about

line 14: 25473 Segmentation fault (core dumped) "$dirname/$appname" "$@"

I get the feeling it is having an issue with the dirname and or appname variable?

My launcher starts up and I can see the login screen but then it crashes

Alright, makes sense I suppose.


stop the display server, use modprobe to unload the old module, load the new one and start up the display server again. Technically, you don't ever need to reboot, with the exception of kernel updates, which in many cases you don't need anyway. But for most machines, rebooting is just easier.

Just wanted to report my success.

Firstly, for whatever reason ./evelauncher did not work, it complained about not finding xbc but it was indeed installed.

Moving forward, sh evelauncher.sh worked and it installed and updated but when I clicked play it acted like it was going to do it's thing but reverted back to pre-play clicking. Looked at the terminal and some error complaining about not seeing Steam so I installed and ran steam and then went back to "sh evelauncher.sh" and it ran without any issue.

Thank you very much for this, tho I do not consider myself a fresh out of the womb noob, I will say I am fairly behind the curve when it comes to fixing issues and im running Debian 8, well that's not entirely true, the Mint version of Debian and last time I tried to install wine in synaptics it said something to the affect that all sorts of things were going to be uninstalled and I didn't want to hose my system and passed on it, that and this particular machine is a bit slow and didn't want to take the performance hit on an already slow box. Long story short, guess I already failed... but thank you again for this and how it allowed me to avoid using wine, tho eventually ill have to man up as there is another program id like to install but that is neither here nor there.

Oh, and happy New Year!