Bug 218979 - Konsole hangs at initial tab completion
Summary: Konsole hangs at initial tab completion
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.3.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 20:47 UTC by Andreas Kern
Modified: 2011-03-04 20:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kern 2009-12-16 20:47:54 UTC
Version:           2.3.3 (using 4.3.3 (KDE 4.3.3), 4.3.3-4.fc11 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.30.9-102.fc11.x86_64

After konsole startup, initial tab completion takes up to 20s, e.g. by typing "mpl" and then hitting the Tab-Key twice). During this time, the complete window does no respond nor is refreshed (blank window after switching to another window and back) neither a new konsole can be opened.
After the initial delay, completions run as usual, new konsole open fast and everything runs smooth, until all instances of konsole are closed. After another startup, the same behaviour occurs.
Comment 1 Matthew Woehlke 2009-12-24 01:36:15 UTC
Since tab completion is a function of bash, it is odd that tab completion should affect Konsole. My guess is maybe this has to do with the tty bell. Do you see the same behavior with 'printf "\a"' in a fresh shell that hasn't had this delay yet? (And if so, does that "substitute for" the delay in tab completion, i.e. if you do 'printf "\a"', that is slow but first tab completion is fast?)

I tried the above, and with sycoca out of date, the bell caused a sycoca rebuild, which very much resembles your stated symptoms. You might want to try running konsole from within itself (or another terminal) and see if there are any messages printed when the 'hang' occurs.
Comment 2 Kurt Hindenburg 2011-03-04 19:49:39 UTC
Have you been able to reproduce on a later version?  4.5.x or even 4.6?
Comment 3 Andreas Kern 2011-03-04 20:29:41 UTC
Newer version's aren't exhibiting this behaviour any longer.