Nick Rout <[EMAIL PROTECTED]> writes: > The point being that when you upgrade kde the environment variable > may not be reset until you re-read those files (which I think > happens if you run env-update).
Haa that sounds like a very likely suspect and also a command I'd completely forgotten. I haven't checked it out yet just added that bin manually to my path but thinking about it here. I didn't upgrade kde recently, what I did was unmerge a number of what I took to be unneeded packages. I ran `equery depends ..' on all before unmerging and saw nothing there to raise an alarm. I sort of missed the thread that I noticed just now about how to purge kde so I was just using my own scheme. Is that scenario likely to require a reread of the scripts you mention or is it only an update that falls in there. More info.. Just now decided to check a bit before posting, I'm a little puzzled with the results. What I did: grep -rin 'kde.*bin' /etc/env.d /etc/env.d/45kdepaths-3.5:1:PATH=/usr/kde/3.5/bin /etc/env.d/45kdepaths-3.5:2:ROOTPATH=/usr/kde/3.5/sbin:/usr/kde/3.5/bin So yup, that is where it gets set but notice I'm running 3.4 so that wouldn't have help me. Then: equery belongs /etc/env.d/45kdepaths-3.5 [ Searching for file(s) /etc/env.d/45kdepaths-3.5 in *... ] kde-base/arts-3.5.0 (/etc/env.d/45kdepaths-3.5) Aha, here is the rub. I did uninstall kde-base/arts-3.4 and 3.5 since somewhere, I think a post of Holly's it was said it wasn't too essential and running `equery depends' on it seemed to bear that out. And in truth, it is not really essential. So, I'd be willing to bet and I'll soon find out that my uninstalling arts-3.4 is what caused my problem, ie my .xinitrc line without absolute filename to startkde (including path) failed. I guess the puzzler here is how kde-arts-3.5 ever got installed since I'm running 3.4. I didn't install it manually, it must have been pulled in by an update world. -- gentoo-user@gentoo.org mailing list
