Bug 1134422 - Mouse cursor corruption
Summary: Mouse cursor corruption
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1141491 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-27 13:40 UTC by Terry Moschou
Modified: 2015-06-29 22:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:17:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Corrupt mouse cursor photot (300.82 KB, image/jpeg)
2014-08-27 13:40 UTC, Terry Moschou
no flags Details
Xorg log file (41.05 KB, text/plain)
2014-08-27 13:41 UTC, Terry Moschou
no flags Details

Description Terry Moschou 2014-08-27 13:40:09 UTC
Created attachment 931473 [details]
Corrupt mouse cursor photot

Description of problem:
I peformed a fresh install of Fedora 20 KDE X86_64.
After a system update and reboot the system exhbited corupted graphics under the cursor (a rectangular reigon) and the cursor itself appears to have been squashed vertically by half.

Booting back into the original kernel from my fresh install and the system reverts back to the intended behaviour.

This bug appears related to https://bugs.freedesktop.org/show_bug.cgi?id=79809
reported against Wayland/weston, which I am not using.

Version-Release number of selected component (if applicable):

Installed kernels:
kernel-3.11.10-301.fc20.x86_64 (Works)
kernel-3.15.7-200.fc20.x86_64 (Fails)
kernel-3.15.10-200.fc20.x86_64 (Fails)

xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64
xorg-x11-server-1.14.4-11.fc20
xorg-x11-server-utils-7.7-6.fc20.x86_64

How reproducible:
Everytime I boot into kernel 3.15.7 or 3.15.10

Additional info:
Hardware:
AMD A6-6310 APU with AMD Radeon R4 Graphics

Comment 1 Terry Moschou 2014-08-27 13:41:51 UTC
Created attachment 931474 [details]
Xorg log file

Comment 2 Hin-Tak Leung 2014-09-16 19:50:02 UTC
*** Bug 1141491 has been marked as a duplicate of this bug. ***

Comment 3 Hin-Tak Leung 2014-09-16 19:53:28 UTC
Mine have slightly different hardware, but a better description and also a photo. Also note that screenshot captures uncorruptedness (hence need an outside camera). I use gnome classic, and did not boot the earliest since install so cannot confirm/deny it being a regression.

Comment 4 Hin-Tak Leung 2014-09-19 05:45:21 UTC
(In reply to Terry Moschou from comment #0)
> Booting back into the original kernel from my fresh install and the system
> reverts back to the intended behaviour.
...
> kernel-3.11.10-301.fc20.x86_64 (Works)

I tried that also - and indeed it shows a good cursor. But I also found that this piece of info is bogus - kernel-3.11.10-301.fc20.x86_64 does not load the drm module nor the radeon module, so I guess it is just operating in generic vesa mode. kernel-3.15.10-201.fc20.x86_64 and kernel-3.16.2-200.fc20.x86_64 loads drm and radeon and shows a corrupted cursor.

You can look at lsmod and 'dmesg| grep drm' to see.

Comment 5 Hin-Tak Leung 2014-09-20 02:22:42 UTC
(In reply to Terry Moschou from comment #0)
...
> This bug appears related to
> https://bugs.freedesktop.org/show_bug.cgi?id=79809
> reported against Wayland/weston, which I am not using.
...

Actually that's relevant - I arrived at it differently. I mentioned my mouse cursor problem at the video suspend/resume bug at kernel bugzilla and one of the responders says that I needed a more up-to-date xf86-modesetting (which is mentioned in the wayland/weston bug where the bug fix was committed to) for the cursor problem:

Indeed, grabbing some rpm's from koji for the upcoming f21 and rebuilding them fixes this problem for me:

# diff rpm-pre-fix rpm-post-fix | grep -E '(<|>)'
< xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64
> xorg-x11-drv-ati-7.4.0-3.fc20.x86_64
< xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64
> xorg-x11-drv-modesetting-0.9.0-2.fc20.x86_64
< xorg-x11-glamor-0.5.1-3.20140115gitfb4d046c.fc20.x86_64
< xorg-x11-glamor-devel-0.5.1-3.20140115gitfb4d046c.fc20.x86_64
> xorg-x11-glamor-0.6.0-3.20140419gita4fbc77.fc20.x86_64
> xorg-x11-glamor-devel-0.6.0-3.20140419gita4fbc77.fc20.x86_64

(note you cannot just grab the binary f21 rpms, as the server versions between f20 and f21 are differnt and abi not binary-compatible)

I am also updating the ati driver/glamor to try to get X-video to work (not yet, it looks like I need newer mesa/llvm also), but I believe a newer xorg-x11-drv-modesetting alone may be sufficient to fix this.

Comment 6 Fedora End Of Life 2015-05-29 12:44:41 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-06-29 22:17:02 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.