Summary: | first tab/menu halts konsole for a few seconds | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Vinay S Shastry <vinayshastry> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.6 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Vinay S Shastry
2005-12-05 07:53:42 UTC
This is known. The "entire" menu structure is not automatically created when Konsole starts up, only when the user firsts uses the menu (top menu or mouse menu). Konsole reads files under $KDEDIR and $KDEHOME; perhaps that is why it reads mtab. What does reading an environment variable have to do with mtab and pausing for 4 seconds ? besides.. the main issue i face is the new tab.. what does that have anything to do with mtab and meminfo ? it wasnt happening in kde 3.4.X .. I'm sure something has crept in with 3.5.. Not environment variables... all the config files for KDE and Konsole are under $KDEHOME and $KDEDIR.... For example: % echo $KDEDIR /opt/KDEDIRS/branches/3.5 % echo $KDEHOME /home/kvh/.kdehome-3.5 This is nothing new... there are a few more options but the delay should be about the same in KDE 3.4.x my query is.. why does this happen only for first tab in a konsole window and not on second, third or any other attempts ? This has to do with when the entire menu structure is loaded. Nothing to do in KDE 3.5. Hopefully will be 'fixed' in KDE4 |