-   Linux - Desktop (
-   -   RHEL 5.5 w/ KDE 3.5 Konsole closes on it's own (

boblc123 09-13-2013 10:58 AM

RHEL 5.5 w/ KDE 3.5 Konsole closes on it's own
Dear Linux Experts

At my company we are running RHEL 5.5 with KDE 3.5. I recently had to re-kickstart my box and now I'm having issues with my konsole automatically closing on it's own. I never experienced this problem until I re-kickestarted and none of the other boxes are having this problem. Here's how to recreate it:

Open a konsole window. Do nothing else except for stare at the computer screen for about 20 minutes. The konsole window will magically close on its own. I've noticed that it will not close on its own if you're tailing a log or something.

My suspicion is that there's a setting somewhere within kde that I can change to fix this but I can't find anything of the like. My company will not allow me to post logs or config files online, but I can tell you that /var/log/messages shows no problems.

Anybody got any ideas?

John VV 09-13-2013 05:42 PM

have you asked your IT Dept. to contact redhat ?
you ARTE paying them a boatload of cash to keep it at RHEL5.5 and not the current older 5.9

redhat tech support should be able to help your it dept.

is the screensaver turned off ?
10 min. is the default but it might be 20
the same for the "power saver" - it is part of the screensaver gui ( on gnome it is )

for the old kde3.5 ?
look in the system configure menu
it will be in there someplace

seeing as you can NOT post the log files
have you read them and looked for an error

what about other terminals
there should be a few terminal emulates installed

boblc123 09-13-2013 07:44 PM

I am part of the IT dept. But I wanted to try and resolve the issue here first, before putting a ticket in with Redhat. I figured I'd learn more this way.

As for the logs, the only log that I know to look at for this would be /var/log/messages. Any idea on what other logs I can look at?

I don't think the screensaver has anything to do with it because I have my screensaver set at 30 mins and the konsole window will close before the screen saver kicks on.

I will look in the system configure menu when I go back to work.

John VV 09-13-2013 08:19 PM

it has been a bit since i used rhel5

you are on kde so is dolphin or konqueror used

dose "xterm" also die after 20 min.

one thing you could do is create a test user on this machine
and see if that user has the same problem

in your current user rename .kde to .kde.old
and log out and back in

boblc123 09-16-2013 03:09 PM

I'm using Konqueror

xterm also dies after 20 mins

I've tried renaming .kde folder and reinstalling video drivers because I'm seeing some "X Error: BadWindow (invalid Window parameter) 3" errors in the .xsession-errors file. Neither of which resolved my issue.

I also logged in as a different user and this problem still exists. Therefore, it has to be an issue with the box and not any single user account.

John VV 09-16-2013 03:17 PM

I am at a loss to

if only the terminal window is turning off after 20 min. of use
that is something odd

there should not be a time limit on the length of time you can use a terminal

that would kill a long update in it's tracks

if it were to shut down during a long update that would be a disaster .

boblc123 09-16-2013 03:22 PM

Well it seems to only happen if nothing is going on in the terminal window. For example:
If I just open up terminal and cd to a directory then get side tracked and leave my desk, when I come back the window is gone.

However, if i open up a terminal and tail -f a log, or run a script that takes a long time to complete, my window will stay open with no problem.

John VV 09-16-2013 04:24 PM

Are you referring to the " lock screen"

if you leave your desk for 5 min or 10 or 20 min. ( 15 min. is the default)
the system WILL auto lock the computer

do you have to type in your user password again ?

boblc123 09-16-2013 06:35 PM

No, I changed my lock screen to come on after 30 mins. I'm not talking about the lock screen.

My konsole/xterm window will actually disappear and it's PID is gone. So something is actually killing that process.

John VV 09-16-2013 07:26 PM

this is what the redhat tech support is good for

this is an odd issue

All times are GMT -5. The time now is 06:52 PM.