| Summary: | konsole gets unusable some time when using TAB for completing file or directory names | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | David <StormByte> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
David
2008-01-19 19:52:36 UTC
> all konsole (and its other tabs if are opened more than one)
> gets unusable and does not respond to events in some time (arround 1 minute).
Does CPU usage increase during this time? If so, can you open System Monitor during the pause and check which process is using the CPU.
Do you experience this behavior in other terminal programs (eg. xterm)?
Is this pause triggered by anything else. If you press the tab key when filename or command completion is not expected for example.
> This is proven in latest SVN snapshot.
Which SVN revision? You can find this out by running "svn info <path to kdebase>"
Ok, SVN revision is: svn info /usr/portage/distfiles/svn-src/KDE/kdebase/kdebase/ Path: /usr/portage/distfiles/svn-src/KDE/kdebase/kdebase URL: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase Repository Root: svn://anonsvn.kde.org/home/kde Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da Revision: 763967 Node Kind: directory Schedule: normal Last Changed Author: ogoffart Last Changed Rev: 763953 Last Changed Date: 2008-01-20 18:11:56 +0100 (dom, 20 ene 2008) ========================== All other KDE parts are as well latest (same SVN date than this bug report's date). I notified that there is some really strange issue: not only kaffeine stops responding for a short period of time, *ALL* KDE parts do the same: kopete, konqueror, dolphin, kwin (because dialogs also stop responding sometimes after a short period of time).. This does not happen in a not native KDE application (kde3 app, KVirc, for example), so maybe the problem is within KDE libs. For more info, I don't have kde3 installed at all (only kdelibs for compatibility with kde3 programs I use (knetworkmanager, KVirc and Amarok 1.x). Please, redirect me to where you need to, I don't know to whom speak to solve this issue, or to work with it. I can give more info if asked to. A question to test: Does any KDE4 thing uses some KDE3 parts? If so, do you advise me to install a KDE3.5.8 Desktop as well as KDE4 and retest? Thanks, David. CPU usage does not increment, but as I said, this is not only in konsole is in almost all KDE4 things. Rober, can you assist me a bit? I think the real problem is in WM, maybe KWIN. As a example, this bug I can reproduce in every window that pops up: confirm delete files (from dolphin), when I open kmail (I need to wait a bit before it responds to events), but this doesn't happens always, it happens at least once, and once it happened, I can use apps normally. In case of konsole isn't this way: konsole is usable everytime I start it, and this problem happens a bit later. > Rober, can you assist me a bit? I think the real problem is in WM, maybe KWIN
Does the problem still occur when using a different window manager?
Install metacity for example and run "metacity --replace" and see if the problem is still present.
Well, I've been testing metacity and I can say that KDE works far better while still having little issues. For example "most" of the windows that are displayed, have correct focus now (with KDM, for example you couldn't click a button sometimes as the window was some kinda hanged some times). Maybe it means that KDEWM is a bit broken somewhere? Or is a compositing issue? (with metacity I don't have compositing...) I want to point out also that maybe there are problems in port of KDEUI classes too, but anyways, KDE4 is far more stable with metacity than with KWin > Well, I've been testing metacity and I can say that KDE works far better while still having little issues.
What about this particular bug report? If switching the window manager from KWin to Metacity makes the problem with TAB go away then this report needs to be re-assigned to KWin so the right people can look at it.
I'd say that this is gone, but let me at least two days for more testing. Sorry for the fast re-report, but this bug isn't gone with metacity. This time, it happened to me when opening konsole and type "/usr/src/li<TAB>" as root. But as this does not happens always.. :( Robert, I discovered that this is highly probable related to composite effects in KDE. As I deleted ALL kde config and restarted session, and I cannot reproduce this behaviour in any kde app (not like before). Can this be CCed to someone else? > I discovered that this is highly probable related to composite effects in KDE.
Okay. Re-assigning to KWin.
I have a problem following the logic in comments #11 and #12 - #11 says the problem exists even with Metacity, i.e. without KWin, but in #12 suddenly it's a KWin problem, just because you cannot reproduce it after deleting KDE config? So, did this problem exist only when compositing was enabled in KWin or not? Re-assigning back to Konsole. Sorry Lubos, I didn't read the replies carefully enough. Hello, This is a duplicate of a problem with KDE's system notifications which is now fixed. |