Bug 1573073
| Summary: | Konsole ignore scrollback settings | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jordan Metzmeier <jmetzmeier01> |
| Component: | konsole5 | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | jmetzmeier01, rdieter |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-30 15:29:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jordan Metzmeier
2018-04-30 06:23:59 UTC
The only change fedora makes to stock configuration is to set
scrollbackUseCacheLocation
to true by default, ie,
settings -> configure konsole -> file location -> use user specific location
(but that's only relevant if one uses unlimited scrollback).
That said, I cannot reproduce.
I create a new profile, set scroll back to 2000, then select
File -> new tab -> new profile
and run,
for i in {1..2000} ; do echo $i; done;
and my scrollback includes all of it.
I can see that default is set to ~/.cache/konsole. I checked that directory on my machine, and it is empty. I just tried changing that to /tmp and restarting konsole, but no new file was created in /tmp. Running "for i in {1..2000} ; do echo $i; done;" only scrolls back to "931".
Thanks for looking into the issue.
FYI, that custom dir is only used if you set *unlimited* scrollback, otherwise, it's save in memory I was actually able to resolve the issue by creating a new profile and switching to that (without any changes). When I switch back to the original profile it still works. I assume for some reason it wasn't using any profile. Since this looks like an issue on my end, we can close this bug. Thanks for the help. OK, thanks for the additional testing too |