Bug 203064

Summary: Kblocks sluggish in fullscreen mode
Product: [Applications] kblocks Reporter: Emmanuel Surleau <emmanuel.surleau>
Component: generalAssignee: Zhongjie Cai <squall.leonhart.cai>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andrew.crouthamel, browserbugs2, gilles.di.martino, jesper, johannesobermayr, majewsky, torquil
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Emmanuel Surleau 2009-08-08 11:51:16 UTC
Version:           0.1 (using 4.3.00 (KDE 4.3.0), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.30-4.slh.2-sidux-686

Kblocks feels very slow when the window is maximized (my screen is 1680x1050). There is a delay before the keypress becomes effective which makes the game barely playable. The animation is slow as well (particularly when a row disappears), and the game consumes an unreasonable amount of CPU (which it doesn't do in a smaller window). In fact, it looks like there is a threshold above which the game becomes really slow and CPU-hungry (the game is still fluid in a window of 1100x810).
Comment 1 Johannes Obermayr 2010-03-30 01:02:30 UTC
Assign to Zhongjie Cai as new maintainer.
Comment 2 Christoph Feck 2010-10-29 02:06:51 UTC
*** Bug 253663 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Majewsky 2011-01-02 00:27:22 UTC
Could you start KBlocks from the command line or from KRunner with the command "kblocks --graphicssystem raster", and check if that improves the performance?
Comment 4 Gilles DI MARTINO 2011-01-17 17:37:25 UTC
Le 02/01/2011 00:27, Stefan Majewsky a écrit :
> https://bugs.kde.org/show_bug.cgi?id=203064
>
>
> Stefan Majewsky<majewsky@gmx.net>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |majewsky@gmx.net
>
>
>
>
> --- Comment #3 from Stefan Majewsky<majewsky gmx net>   2011-01-02 00:27:22 ---
> Could you start KBlocks from the command line or from KRunner with the command
> "kblocks --graphicssystem raster", and check if that improves the performance?
>
i tried your command line and it's muchbetter !
Thanx for your advice.
Comment 5 Emmanuel Surleau 2011-02-06 23:31:17 UTC
Ditto for me, raster makes a huge difference.
Comment 6 Christoph Feck 2011-07-11 15:18:04 UTC
*** Bug 270458 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2011-07-11 15:18:56 UTC
*** Bug 268583 has been marked as a duplicate of this bug. ***
Comment 8 Gérard Talbot (no longer involved) 2011-09-11 01:41:40 UTC
Stefan Majewsky,

I started KBlocks version 0.3 from the command line "kblocks --graphicssystem raster" and got this message:

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No file or folder of such type
QFileSystemWatcher: failed to add paths: /home/gerard/.config/ibus/bus

Like many others, I find KBlocks slow, sluggish; there is a small delay before the keypress becomes effective which makes the game not as fun.

Using
KDE platform: version 4.7.0
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic-pae i686 (32bits)
Screen resolution: 1024 x 768
Screen Refresh rate: 85 Hz
Kubuntu 11.04 
here.

regards, Gérard
Comment 9 Andrew Crouthamel 2018-11-06 15:09:17 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Jesper Goll 2018-11-15 13:34:54 UTC
I don't think I have been involved with this bug before, but I received a request for a retest, so:

Having tested Kblocks today on an updated Tumbleweed system (OpenSuse Tumbleweed 20181112, KDE Plasma 5.14.3, KDE Frameworks 5.51.0, Qt version 5.11.2, Kernel version 4.19.1-1, 64-bit, Thinkpad P70), I could find no trace of any sluggish response when running in full-screen, or otherwise. (Mind you, a Thinkpad P70 is sort of high-end as far as laptops go, so it might not be the best testing platform for this.)

My test does not prove, of course, that such a problem does not exist on some present-day systems ... but perhaps it would be better to close this bug now, since this is a performance issue, and the technical setting in which it occurred would seem to be long gone by now. If this was still an issue, one would think that this bug report, or similar reports, would have seen some activity after 2011.
Comment 11 Andrew Crouthamel 2018-11-15 22:52:19 UTC
Thanks for the update!