http://qa.mandrakesoft.com/show_bug.cgi?id=3848
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2003-03-07 07:37 -------
Buchan,
You are referring to what I consider to be a design flaw in msec.
There is a bug report out on this. But in any case, this effect should
never have happened.
Although msec's half-baked permissions scheme definately contributes to
the effect, I have yet to discover just why.
It's strange. This problem has existed ever since I installed 9.1,
even when logged in as a freshly created user. Is it possible some
combination system settings that only I use causes it? I suppose.
Last week, after a couple of big installations, I stopped seeing the
problem. Unfortunately, I hadn't kept good notes.
So for now, I'm closing the report.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
Since installing Mandrake 9.1, I have had a terrible time with KDE. The main
problem was extreme slowness, in KDE startup, and startup of all KDE apps.
Non-KDE apps are not affected, but KDE apps are still affected under Gnome. I
later installed KDE 3.1.1 from the Cooker rpm's, with no improvement.
We're talking 5 min to start KDE, and 15-20 sec to start the simplest KDE app.
I have found out the combination of things that causes this effect.
1) fam daemon running
2) msec level 4
3) user with adm priviliges (or equivalent access)
Now, I don't know why I even had fam running. I've since turned it off. But I
don't think it should have been doing this.
And it doesn't, unless you set the system security level to 4. Then msec shuts
down permissions to all sorts of things users are familiar with, such as 'ps'.
To give a user access to such things, one can put the user in group 'adm'.
On next boot-up, KDE will be a horrible pig.
