Dale wrote:
Well some seemed to have no issues with it and just changing the USE
flags was it. Not for me tho. Got locked out of my own system with
no mouse or keyboard. I never did get that thing to work either.
This however seems to have worked. I emerged them, ran etc-update
which had a LOT of updates, went through the guide and edited a few
things and rebooted. I can't say it was any faster tho. It stopped
at one point, which worried me at first, then carried on. I'm not
sure what it stopped on tho. Maybe it was a one time thing.
What do you know, I upgraded and it worked. Now if I can just get rid
of this Nepomuk thingy that pops up a bit after I login to KDE. Makes
me want to get a fly flap and beat on the message. lol It bugs me.
Get it?
Thanks for the replies. Sort of helped me decide when to do this.
Dale
:-) :-)
I noticed something . . . odd. Sometimes when I do upgrades to some
packages, I go to single user, check what processes are still running
and kill strays, then go back to the default run level and login. I
just updated a lot of KDE related stuff and went to single user. When
it says single user, it ain't kidding. It even unmounts file systems.
Oook. That's weird. It didn't do that before. :/ Then when I wanted
to go back to the default run level and typed in rc default & exit, it
logged me out which is normal but nothing scrolled up like it did in the
old baselayout. The screen went blank and a bit later the KDM screen
came up. It used to be that it logged me out and then I saw all the
services scrolling up until kdm started.
Is this the new normal? Should I not do the exit thing now?
One good thing I noticed, KDE used to have a LOT of dead processes
running after logging out, even after going to single user. Lots of
kdeinit and knotify stuff. It seems to close out a LOT cleaner. On my
first time going single user, it was clean as a whistle. I didn't see a
single stray process in the bunch. Neato !!
Thanks.
Dale
:-) :-)
