I use SLiM, everything was fine in using X, I moved to Xgl, and found this error. So b/c of that I am not sure where this error should go, but I believe it to be a baselayout problem, and will, explain. Background: When I started to have SLiM launch Xgl using it's config file, the screen would be distorted on boot up. I would try to re-emerge something, and then it would work. I found out though that emerging any ebuild would cause Xgl and SLiM to work. Thinking about it I realized that env-update was one of the common commands. I did a fresh reboot and tried it out, and found out that was the fix ... now to what the differences was. Rebooting again, and comparing the fresh profile.env, to what I saved elsewhere that had been generated after a fresh reboot, but caused SLiM and Xgl to work I found it was the LIBGL_DRIVERS_PATH variable the bad one only had /usr/lib32/dri, the working one had /usr/lib64/dri also. Looking in my env.d dir, I found two files 04ati-dri-path-amd64 and 04ati-dri-path-x86. Both of these contain definitions of the same variable, but one to the 64bit dir, and one to the 32bit. And here is where I think is the problem with the env-update used in the baselayout. The one in the baselayout just uses the 32bit definition, it doesn't concatenate the results into one variable. Running the env-update shipped with portage does this. I don't really care which way it is, just think it needs to be consistent :) I'll attach the bad (fresh boot) and the good (portage env-update) to this bug so both can been seen. The diff between the two is below < export COLON_SEPARATED='LIBGL_DRIVERS_PATH' 26c25 < export LIBGL_DRIVERS_PATH='/usr/lib32/dri' --- > export LIBGL_DRIVERS_PATH='/usr/lib64/dri:/usr/lib32/dri' So the LIBGL_DRIVERS_PATH isn't concatenated, and the COLON_SEPARETED is read in, but isn't by portage's env-update. If you need any more info let me know.
Created attachment 117360 [details] profile.env.bad
Created attachment 117362 [details] profile.env.good
Fixed in our svn repo, thanks for the heads up.
*** Bug 176179 has been marked as a duplicate of this bug. ***
Should be fixed in alpha2
Yes it was, sorry, forgot this bugs was still open.
