Bug 139202 - terminal properties queried during early stages of session restoring wrong? or missing?
Summary: terminal properties queried during early stages of session restoring wrong? o...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2006-12-25 06:13 UTC by Roland Eggner
Modified: 2018-09-19 14:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Eggner 2006-12-25 06:13:51 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

My most enjoyed features of KDE are
- ALL keybindings user configurable
- klipper remembering all old clipboard entries even from previous KDE sessions, limited only by hd-space, WITH incremental search
- powerful session restoring

Want to contribute an issue for even further improvement:
In most (all?) cases
(1) restored mc-sessions lack subshell as if launched by "mc -u" - VERY ANNOYING
(2) restored shell sessions of type "tail -F -n 200 /var/log/xxx" lack actual COLUMNS-value = 201 in my case, lines are wrapped to 80 columns leaving more than right hand half of screen empty - less annoying because concerns only "old" content of logfile I want to follow

I suppose the two problems share the same reason, namely terminal properties queried during early stages of session restoring are wrong or missing.

I am using this NOT always but mostly successful workaround:
konsole - settings - sessions:
name: mc
command: /bin/sh /usr/local/bin/WaitCpuLoad.sh; mc -c

with this WaitCpuLoad.sh:
#!/bin/sh
until (( "$(sed -re 's,^0?([0-9]*)\.([0-9]).*$,\1\2,' /proc/loadavg)" < 16 )) ; do
        sleep 10
done

Wish: workaround is a mess, konsole should manage the necessary delay itself until KDE is up and settled, should not try to stay ready even prior to KDE.
Comment 1 Roland Eggner 2007-04-27 23:47:09 UTC
Issue concerns KDE_3.5.6 also.

In the meantime added a line to my above mentioned WaitCpuLoad.sh:

#!/bin/sh
[ -n "$( find ~ -maxdepth 1 -name .Xauthority -mmin -2 )" ] && sleep 30
until (( "$(sed -re 's,^0?([0-9]*)\.([0-9]).*$,\1\2,' /proc/loadavg)" < 16 )) ; do
        sleep 10
done
Comment 2 Kurt Hindenburg 2009-03-08 17:43:35 UTC
KDE3 is not maintained anymore.  Have you tried this with a KDE 4 version?
Comment 3 Andrew Crouthamel 2018-09-19 04:31:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-09-19 14:37:07 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.