Version: 2.3.3 OS: Linux It happens always. It seems the CPU priority is not the highest and has no way to set. This is too annoying so that I switched to gnome terminal, which does not have this problem. Reproducible: Sometimes Steps to Reproduce: 1. open some softwares, e.g. firefox and rhythmbox/amarok...... 2. make programs in konsole for some time Actual Results: switch to gnome terminal Expected Results: use gnome terminal User is able to make the gnome terminal as default in KDE. Gnome did that since they are confident about their terminal. n/a
If you want to get the problem(if it does exist in konsole) fixed, please provide clear steps to reproduce it, or at least express clearly what the problem is. Complaint and sarcasm do not make any help. I can not understand your problem , because the description is quite ambiguous and unclear: 1). open some softwares: open it from konsole? or from krunner or menu? 2). make programs in konsole for some time: run 'make' or what does that mean? 3). actual and expected result: that is sarcasm and opinion, not what has and should have happened. An non-understandable bug report will not be fixed, but be closed as INVALID. Please understand this. By the way, konsole-2.3.3 is quite old(almost 2 year ago). Consider using some recent version of konsole and KDE.
1). open some softwares: open it from konsole? or from krunner or menu? From both. I did a firefox,a rhythmbox or VLC from menu on KDE4.3.2 and some emacs. make CPU% to 20%~50% with enough free memory. 2). make programs in konsole for some time: run 'make' or what does that mean? OK, in other words, you just do some text jobs in konsole.Keep typing some long commands 3). actual and expected result: that is sarcasm and opinion, not what has and should have happened. It should work smoothly and display all characters typed from the keyboard, not stop 2-3 secs in very five to ten minutes. Expect the KDE can choose default web browser, terminal, file browser.... On 2011/8/23 3:22, Jekyll Wu wrote: > https://bugs.kde.org/show_bug.cgi?id=280583 > > > Jekyll Wu<adaptee@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |adaptee@gmail.com > > > > > --- Comment #1 from Jekyll Wu<adaptee gmail com> 2011-08-23 01:22:49 --- > If you want to get the problem(if it does exist in konsole) fixed, please > provide clear steps to reproduce it, or at least express clearly what the > problem is. Complaint and sarcasm do not make any help. > > I can not understand your problem , because the description is quite ambiguous > and unclear: > > 1). open some softwares: open it from konsole? or from krunner or menu? > 2). make programs in konsole for some time: run 'make' or what does that mean? > 3). actual and expected result: that is sarcasm and opinion, not what has and > should have happened. > > An non-understandable bug report will not be fixed, but be closed as INVALID. > Please understand this. > > By the way, konsole-2.3.3 is quite old(almost 2 year ago). Consider using some > recent version of konsole and KDE. >
Thanks for the reply, which is more useful than the original report. But I can't reproduce this problem, even in a gentoo system which is busy with compilation. I will suggest again upgrading your system and KDE to a recent version, if possible. KDE-4.3.2 is quite old compared to KDE-4.7. Even Debian stable does not ship such an old version(it ships KDE-4.4.5). Your problem may be a solved problem.
compilation won't reproduce the problem. That's mainly due to the kwin process intervention, again I guess. Besides that, npview.bin (the flash player) in Firefox some times also plays a bad role. I mean that you may need to run something heavily taking the graphic card but not the main CPU. As a remembered I had this problem while I was using KDE2.X with Firefox on. On 2011/8/23 6:47, Jekyll Wu wrote: > https://bugs.kde.org/show_bug.cgi?id=280583 > > > > > > --- Comment #3 from Jekyll Wu<adaptee gmail com> 2011-08-23 04:47:10 --- > Thanks for the reply, which is more useful than the original report. > > But I can't reproduce this problem, even in a gentoo system which is busy with > compilation. > > I will suggest again upgrading your system and KDE to a recent version, if > possible. KDE-4.3.2 is quite old compared to KDE-4.7. Even Debian stable does > not ship such an old version(it ships KDE-4.4.5). Your problem may be a solved > problem. >
Well, I tried playing a high-quility video which puts heavy work on GPU and didn't notice the problem. Please upgrade your system then check this issue again. I guess no KDE developers have such an old system, or are interested with investigating some problem in a very old version.
Thanks. I think you can close this. I noticed that in most cases, the stopping responding is mainly due to a high CPU usage of process "xorg", though I do not know why and which programs use xorg so much. I googled it and it seems to be a general problem of KDE. On 09/17/2011 06:50 PM, Jekyll Wu wrote: > https://bugs.kde.org/show_bug.cgi?id=280583 > > > Jekyll Wu<adaptee@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution| |WAITINGFORINFO > > > > > --- Comment #5 from Jekyll Wu<adaptee gmail com> 2011-09-17 16:50:21 --- > Well, I tried playing a high-quility video which puts heavy work on GPU and > didn't notice the problem. > > Please upgrade your system then check this issue again. I guess no KDE > developers have such an old system, or are interested with investigating some > problem in a very old version. >