Re: [opensuse] konqueror browser
- From: Seth Arnold <seth.arnold@xxxxxxx>
- Date: Fri, 20 Jul 2007 13:44:31 -0700
On Sat, Jul 14, 2007 at 08:30:27PM -0400, Michael Derek Barnett wrote:
If you have been playing around with it, go back through the apparmor
profiles just to make sure you didn't set one on konq.
Do note that setting an AppArmor profile on ANY KDE application is
liable to give strange problems due to KDE's process model.
AppArmor attaches profiles to programs at exec() time, based on the
image that is used to execute the new process.
KDE starts a single process, kdeinit, that incurs all the runtime
startup costs associated with creating a new process. A typical KDE
application links in a ton of libraries; this takes time. KDE avoids the
startup time when creating new programs by simply cloning the kdeinit
task and jumping to the entry point in the right library to run whatever
program you need.
The upshot of all this is that if you run 'konqueror', it will simply
notify kdeinit to create a new instance of itself and run the konqueror
The first time a KDE program is run, it sets up this machinery..
So if you confine any KDE application, you run the risk that all your
KDE applications will run under that profile.
You can set the following environment variables to force KDE to avoid
the fast-start procedures, and allow more sane use of AppArmor profiles
Hope this helps :) (though sadly not the original poster..)
Description: PGP signature
- Prev by Date: Re: [opensuse] How toooo
- Next by Date: [opensuse] Re: Firefox tab focus stops working
- Previous by thread: Re: [opensuse] konqueror browser [SOLVED]
- Next by thread: [opensuse] How to auto-delete trash