Bug 257257 - Stones flicker when hovering the board if using the fglrx driver
Summary: Stones flicker when hovering the board if using the fglrx driver
Status: RESOLVED WORKSFORME
Alias: None
Product: kigo
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Sascha Peilicke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-18 18:05 UTC by José Tomás Atria
Modified: 2023-01-14 05:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description José Tomás Atria 2010-11-18 18:05:06 UTC
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

Kigo worked and looked perfectly in this machine until i moved from the free radeon driver to the propietary fglrx driver.

Now the floating stone that replaces the mouse cursor when hovering the board is flickering, and disaperars if you stop moving it. It is very distracting, and makes kigo almost unusable.

Reproducible: Always

Steps to Reproduce:
On a machine with an ATI video card and the fglrx driver, start a new kigo game and move the mouse over the board.

Actual Results:  
The stone that replaces the mouse cursor when hovering the board flickers and is not drawn consistently.

Expected Results:  
The stone that replaces the mouse cursor should be solid, drawn with no flickering and move swiftly over the gaming area.

The application worked flawlessly with the radeon driver. I am almost 100% sure that this is not a problem in kigo, but in kwin or in the composition engine, as i remeber it to be a perennial problem with composition until a couple of years ago.

Alas, i hadn't seen it in a long time, and though i have looked for it in other applications, kigo is the only one exhibiting this behaviour right now.
Comment 1 Andrew Crouthamel 2018-11-05 03:14:22 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 2 Andrew Crouthamel 2018-11-17 04:58:25 UTC
Dear Bug Submitter,

This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-15 05:49:09 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-30 05:23:06 UTC
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
mark the bug 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!
Comment 5 Bug Janitor Service 2023-01-14 05:12:13 UTC
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!