Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 52792 - konsole doesn't write to .bash_history [properly]
konsole doesn't write to .bash_history [properly]
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Ben Levenson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2001-08-29 00:44 EDT by pdenis2
Modified: 2007-04-18 12:36 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-29 00:44:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description pdenis2 2001-08-29 00:44:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.7-pre3.asl i686)

Description of problem:
Commands entered on konsole are not recorded in .bash_history unless
konsole is exited by **typing** exit.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. open konsole; type some commands
2. close konsole either with file/quit or close button
3. open konsole; try up arrow or 'tail .bash_history' --commands are gone
4. (alternative): in step 2 close konsole by typing "exit".  
5. open konsole; up arrow or "tail .bash_history".	

Actual Results:  commands entered in step 1 are not available for recall in
step 3.  

Expected Results:  behave like xterm or any other term

Additional info:

This is discussed and reported fixed (8/27/01) as bug 31339 @bugs.kde.org
so it's a kde bug.

If it is indeed fixed, please incorporate into a new package ASAP.
[I thought 1) I was losing my mind; 2) bash was badly broken; 3) ?!!? ]
Comment 1 Bernhard Rosenkraenzer 2001-08-29 14:27:52 EDT
Fixed in 2.2-9

Note You need to log in before you can comment on or make changes to this bug.