[Konsole-devel] [Bug 184964] Konsole crash taking down ALL Konsole instances

Robert Knight robertknight at gmail.com
Tue Jun 9 22:53:00 UTC 2009


--- Comment #16 from Robert Knight <robertknight gmail com>  2009-06-10 00:52:56 ---
> As far as application init, how about having a
> new instance fork() the old one? ;)

I don't know whether that is possible once the application is up and running
complete with GUI.  That still leaves you without the sharing features - like
being able to move tabs between windows - I'll get to that later.

> Konsole already stores the scrollback in a tmp file. 

Only for the 'unlimited' history mode, not currently for the limited scrollback
used by default.  Do-able though. 

> 2/3 are not really needed
> if the crash handler saves our ptys. ;)

True - although depending on the effort involved it might not be worth it just
for handling crashes in the terminal which, while potentially very annoying,
happen rarely.  

An alternative setup which one of the trolls suggested to me was having a
helper program like GNU-Screen with no GUI be responsible for setting up the
terminal and possibly storing the output - which communicates with the Konsole
UI processes.  Although then you then have the possibilty of that crashing as
well - and bam, you're back to square one.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the konsole-devel mailing list