Session mismanagement

[Lubos Lunak]

On Tuesday 30 of September 2003 15:22, Ian Reinhart Geiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 30 September 2003 08:43 am, Lubos Lunak wrote:
> > > Like i said this has been arround for ever, its just been more extreme.
> > >   One thing i think agrivates it is the "oh you changed the
> > > font/style/color, i am going to crash a random konqi, or two" bug, and
> > > if you have open documents via kio, that take a while to upload.  KSirc
> > > has agrivated this
> >
> >  There's a difference between session files (in
> > $KDEHOME/share/config/session) and temporary KIO files. Are you sure
> > you're not confusing them here?
>
> Are we saving kio temp files in there?!

 You can check yourself (*Ian has a look ... no, nothing like that there*), 
no, we don't save kio temp files in share/config/session.

>
> Afaik these files are all session files stored in that directory.
>
> >> its just
> >> "session managemnt" is one of those things that seems to be a nice thing
> >> if it worked.
> >
> > Well... there must be some secret competition going on about who breaks
> > SM the most.
>
> Hrm... possibly Icepak, followed by gimp, and now possibly appletproxy if
> you start an applet outside of kicker...  but i think this is limited to my
> machine at this point...
>
>
> Is it possible that a b0rked session file on being restored propogates
> itself? ie, if i have  a wacked out konqi that saves its session, could it
> restore a wacked out konqi, that again saves itsself in  a bad state? 

 Technically it is possible.

> Could we also "clear" out unkown session files in there?  Just to keep bad
> files from building up?

 Unknown session file should be equal to unused session file.

>  Or maby "scan" the file and try to restore
> everything in there?

 ??

>
> I think the big issue for me, is that these files build up over time... For
> a user who doesnt know to clean this out they could get very large.   As an
> example, my wifes session on KDE 3.1.4 has 5 konqueror sessions, 8
> konsoles, 2 ksircs, 7kwins and a kopete in her session.  I know for a fact
> I am the only one who uses konsole there, but im pretty sure at least 4 of
> the konqi's are real as well as the kopete...

 So there are about 20 files that are no longer used, taking up few KBs? 
Where's the problem?

 Since there's the report about this in bugzilla, I'll somewhen try to clean 
up old unused files, if you really care so much about it. For the rest of the 
other problems, I suggest you file a bugreport for KDE applications, for 
non-KDE apps you can file them for ksmserver or report them directly for the 
apps.

On Tuesday 30 of September 2003 15:55, Martijn Klingens wrote:
> Kopete unfortunately doesn't support session management at all, it just
> quits on logout. I'd be surprised if you have SM data available for Kopete.

 *surprise* *surprise* If Kopete does nothing related to SM, it means it 
simply uses the basic (restarting) support for SM provided by Qt.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/