On 6/25/06, Benno Schulenberg <[EMAIL PROTECTED]> wrote:
Kevin O'Gorman wrote:
> Killing *all* kalarm* processes required root priv.
You've apparently been logged in to KDE as root once, or done other
weird stuff as root. You may wish to look through /root/.kde* for
things to salvage, and then delete it all. And look through ~/.kde
for files with root ownership (cd ~/.kde; find . -user root).
You're quite right. I hadn't realized it, but I was apparently root when
I was exploring this before: I found that missing alarm that I entered
when the alarms didn't show up. So it was operator error all along --
if I had just been my usual self, everything would have been normal.
I had been working as root a lot to rebuild KDE, and just lost track, I
guess. My bad.
Sorry for the excitement. Thanks for the help.
Everything is normal again.
When you now log back in to KDE (as user, of course), is there again
a kalarmd process owned by root?
> > Press F1, read chapters 5 and 7.
What I meant here, of course, is to press F1 while in the Kalarm
window. :)
Benno
--
[email protected] mailing list
--
Kevin O'Gorman, PhD
--
[email protected] mailing list
