[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Bug#38142: wrong wallpaper list kills xlock (fwd)
From:       Matthias Welwarsky <matze () stud ! fbi ! fh-darmstadt ! de>
Date:       2002-02-15 19:42:00
[Download RAW message or body]

On Friday 15 February 2002 19:32, Rik Hemsley wrote:
> #if Stephan Kulow
>
> > On Friday, 15. February 2002 14:14, David Faure wrote:
> > > Funny, as in: never thought this would happen....
> > >
> > > But seriously... Maybe this is a reason why we shouldn't have
> > > merged kdesktop and kscreensaver (at least the lock stuff).
> >
> > The locking _is_ out of kdesktop. It's in the screensaver that is started
> > from kdesktop. If kdesktop dies, it takes it's children with it, it
> > seems. Solution is to reparent the screensaver. daemon() or what was the
> > name of that function? :)
>
> setsid(2), I think.

setpgid(2) is maybe better, because the screensaver is no session leader. If 
the screensaver should not die when kdesktop dies, move it out of the process 
group of kdesktop. if you open a new session for the screensaver, it will 
probably refuse to die when the real session leader (xsession) is killed...

regards,
	Matze

[prev in list] [next in list] [prev in thread] [next in thread]