Bug 99397

Summary:	Any form of terminating a Konsole, shell, etc. causes the shell to lock up
Product:	[Applications] konsole	Reporter:	Steven Risner <sdrisner>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Steven Risner 2005-02-14 21:10:09 UTC

Version:           unknown (using KDE 3.2.3, SuSE)
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:                Linux (i686) release 2.4.20-64GB-SMP

Every attempt to exit a konsole session causes the shell window to lock up.  Have tried exit command, X, right click quit, close.  Only kill works but the konsole is brought back up in the next session.

Shell is completely function until an attempt to close occurs.

Comment 1 Steven Risner 2005-02-14 21:12:08 UTC

running KDE 3.1.1, on SuSE 8.2, but I am using the KDElibs 3.2.3 (so I can use Kdevelop 3.0.6)

Everything else is fully up to date in terms of SuSE 8.2 packages.

Comment 2 Thiago Macieira 2005-02-15 04:13:06 UTC

Please upgrade to KDE 3.3.2 (or, if possible, 3.4 beta 2) and try again. If you can still reproduce the problem, please reopen.

Code has changed too much since 3.1.1 for us to even verify if such a bug still exists.

Comment 3 Steven Risner 2005-02-15 12:43:10 UTC

I can reproduce it everytime.  I happens with all terminal sessions and with every shell.  The only way I can get them to close is by having the session manager not save the session and start a new one.

The KDE 3.3 will require I revamp most of my system, a very time consuming and risky operation since this is my work machine and the time doing this is not my time.

Is there something I can produce to help resolve this issue.  When the system logs off it must kill the prompts that were either locked or remain open.  There must be some some log entry for this.

If there is no real fix that is forseeable (my workaround was previously mentioned) I will have to settle with this problem.

Comment 4 Kurt Hindenburg 2005-02-15 19:11:24 UTC

No one is running 3.1.x or 3.2.x and hence we can't verify/help.  I'm not sure why you are using different versions, but that likely doesn't help.

I don't even have the source code for 3.1.x nor 3.2.x.