Comment 32 for bug 475891

I just re-read your comment:
"The executable binary tries to open ( and save after work )
"eagle.key" in the same path as the binary is started from.
So if you copy the executable binary to /usr/bin and start
/usr/bin/eagle you will get an error "can not open
/usr/bin/eagle.key",
and for example if you copy the executable binary to /home and start
/home/eagle you will get an error "can not open /home/eagle.key".
There is no way to seperate that two files ( executable binary to
/usr/.... and eagle.key to /home/.... ) also with symlinks, i found no
way."

Thanks for figuring that out, do you have an idea why some users (e.g.
fabrice and I) are able to run the program without segfaulting without
the executable in our /home? The eagle wrapper file we are using just
executes the binary in /usr/lib/eagle in our home directories using
"exec -a"