Version: 2.5 (using KDE 4.5.1) OS: Linux Konsole became very slow (eats up to 50% of CPU while pressing and holding ctrl+o in mc) after I updated to kde-4.5.1, situation became even worse after upgrading to intel graphics stack from git. Keyboard responsibility is really bad, I can notice delay between key press and draw of symbol. Reproducible: Always Steps to Reproduce: Launch konsole, launch mc in it, press and hold ctrl+o Actual Results: Konsole is slow Expected Results: Konsole as fast as possible
Bug is reproducible with xf86-video-intel-2.12.0, mesa-7.8.2 and libdrm-2.4.21 I used sysprof to profile it a bit, and it shows it spends much time in libkonsoleprivate, here's screenshot: http://fenix-fen.at.tut.by/shots/shot-3.png xfce terminal and urxvt and xterm work with no problem on same graphics stack. Other applications are not affected by this bug, so it's definitely some bug in konsole.
> xfce terminal and urxvt and xterm work with no problem on same graphics stack. Those programs are only using part of 'the same graphics stack' - that is, only X.org and below. Everything above X.org is different I believe. > I used sysprof to profile it a bit, and it shows it spends much time in > libkonsoleprivate, here's screenshot: Thanks for looking into this. Unfortunately I won't have the time to try installing the latest Intel drivers to reproduce. There a few more debugging steps that would be helpful: * Run Konsole with '-graphicssystem raster' and compare with '-graphicssystem native' to see whether this makes a difference. * If you have another machine available, it would be interesting to see how your profile of a slow system compares with a profile of a system where it is working better. * Lastly, callgrind/kcachegrind can be used to produce a more detailed profile using: valgrind --tool=callgrind konsole --nofork
It's same with -graphicssystem raster and -graphicssystem opengl. Unfortunately I have no another machine with kde 4.5 installed on it. Will do profiling with valgrind a bit later. Btw, as I mentioned in previous comment, situation is not perfect with latest stable intel graphics stack.
Valgrind is not working due to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=574889
Migrated to XFCE, as it does not suffer from such kind of bugs. Good luck, guys! Keep loosing your users by ignoring bugs and blaming gpu driver developers.
> Good luck, guys! Keep loosing your users by ignoring bugs > and blaming gpu driver developers. That's enough. Nobody blamed driver developers for the problem described in this bug report. What I said in comment #2 was that in order to reproduce the problem I would need to install the same (or at least nearly the same) Intel drivers you are using. Unfortunately, I'm short of time to try that out so you or someone else will have to chip in and help with debugging the problem.
(In reply to comment #6) > That's enough. Nobody blamed driver developers for the problem described in > this bug report. intel devs were blamed by thiago_home at #kde@irc.freenode.org on 19th of September when I asked for help with this bug. I have logs with proof.
> intel devs were blamed by thiago_home at #kde@irc.freenode.org on > 19th of September when I asked for help with this bug. I have logs with proof. I was not part of that conversation. If there was relevant technical discussion, please post the log. Still, as I said before, without more detailed debugging information I'm not able to help so I'm marking this as WAITINGFORINFO for now.
(In reply to comment #8) > I was not part of that conversation. If there was relevant technical > discussion, please post the log. Just same stuff as in this bug report > Still, as I said before, without more detailed debugging information I'm not > able to help so I'm marking this as WAITINGFORINFO for now. Sorry, but I have no this environment anymore, as I migrated from gentoo/kde to xubuntu/xfce. Just wait a bit until someone else hits this bug, I'm pretty sure that it'll happen as soon as major distributions move to 2010Q3 intel graphics stack. Thanks for reply anyway :)
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 set the bug status 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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!