Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 369 - Wrong path for enlightenment 0.16.5-r2
Summary: Wrong path for enlightenment 0.16.5-r2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-27 17:55 UTC by jochem prins
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jochem prins 2002-01-27 17:55:16 UTC
Emerging went ok, after that run enlightenment.install to have .xinitrc setup
for enlightenment. When you try to run startx, xfree will crash due to an
incorrect path for enlightenment in .xinitrc. Change in .xinitrc:
exec /usr/enlightenment, this must be exec /usr/sbin/enlightenment or exec
/usr/bin/enlightenment
Comment 1 Mikael Hallendal (hallski) (RETIRED) gentoo-dev 2002-01-27 18:36:30 UTC
hmm .. not sure what you mean.

Did you have to change to /usr/bin/enlightenment or to /usr/enlightenment in
your .xinitrc?
Comment 2 jochem prins 2002-01-27 19:21:06 UTC
Change .xinitrc to:
exec /usr/bin/enlightenment
Comment 3 Mikael Hallendal (hallski) (RETIRED) gentoo-dev 2002-01-27 19:28:11 UTC
Ah, now I'm with you. enlightenment.install creates the .xinitrc. hmm, ok, this
will be looked into
Comment 4 Bart Verwilst 2002-03-18 11:09:55 UTC
I never used enlightenment in my life, so i really don't think i'm the right 
person for this :( So, like you asked, i'm transferring this back to you so you 
can appoint someone better.. 
Comment 5 Daniel Robbins (RETIRED) gentoo-dev 2002-03-19 16:31:33 UTC
Seemant: can you see if this bug still exists?
Comment 6 Seemant Kulleen (RETIRED) gentoo-dev 2002-03-19 21:10:51 UTC
This bug does still exist.  And apparently it's a known one from upstream. 
OpenBSD and fink both experienced this same issue.  I borrowed the OpenBSD fix
for this.

Thanks for catching this.