Bug 448440

Summary: strange and annoying cursor
Product: [Fedora] Fedora Reporter: Ulrich Drepper <drepper>
Component: xorg-x11-drv-atiAssignee: Dave Airlie <airlied>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 11CC: mcepl, xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 10:38:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Picture of invalid cursor
none
xorg.conf
none
Xorg.0.log files
none
Xorg.setup.log
none
Xorg.0.log
none
Xorg.setup.log none

Description Ulrich Drepper 2008-05-26 21:58:44 UTC
Description of problem:
This problem started when I switch to a dual-head configuration.  The card is an
r600-based ATI FireGL with two dual-link DVI outputs, connected to two 2560x1600
monitors.  The setup uses xrandr to create a spanning desktop.

With the setup the cursor shape frequently changes into something which is no
valid cursor form (see attached photo).  I talk about the vertical saw-like
pattern.  In this case it is right on top of a window frame.

It seems to happen frequently (but not always) when the cursor form has to
change.  Sometimes it's repeatable, other times not.  In any case, within, say,
30 secs of use it's bound to pop up somewhere.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.4.99.901-30.20080519.fc9.x86_64
xorg-x11-drv-ati-6.8.0-15.fc9.x86_64

How reproducible:
unrepeatedly, not necessarily on demand, but pretty quick

Steps to Reproduce:
1.dual-head setup with ATI card
2.just use the machine
3.
  
Actual results:
invalid cursor

Expected results:
no invalid cursor

Additional info:

Comment 1 Ulrich Drepper 2008-05-26 21:58:44 UTC
Created attachment 306709 [details]
Picture of invalid cursor

Comment 2 Matěj Cepl 2008-05-27 10:18:50 UTC
Hi, Ulrich,

can we get your X server config file (/etc/X11/xorg.conf) and X server log file
(/var/log/Xorg.*.log)?

Thanks

Comment 3 Ulrich Drepper 2008-05-27 14:29:35 UTC
Created attachment 306775 [details]
xorg.conf

Hand-generated xorg.conf.  s-c-d couldn't do it.

Comment 4 Ulrich Drepper 2008-05-27 14:41:36 UTC
Created attachment 306778 [details]
Xorg.0.log files

bzip2-compressed Xorg.0.log file

Comment 5 Ulrich Drepper 2008-05-27 14:42:28 UTC
Created attachment 306781 [details]
Xorg.setup.log

bzip2-compressed Xorg.setup.log file

Comment 6 Matěj Cepl 2008-05-27 21:02:12 UTC
Created attachment 306837 [details]
Xorg.0.log

Comment 7 Matěj Cepl 2008-05-27 21:03:28 UTC
Created attachment 306839 [details]
Xorg.setup.log

Comment 8 Ulrich Drepper 2008-05-28 21:21:26 UTC
One more interesting observation:

I had the cursor turn strange while an animated cursor was used (firefox,
submitting a form).  The result was that the strange cursor also was animated. 
I.e., these spinning dots repeated vertically.

I.e., the saw-like form is the result of painting the real cursor form multiple
times vertically, overlaying each other.  In the horizontal direction the cursor
is not wide enough.

Comment 9 Matěj Cepl 2008-05-28 23:04:55 UTC
Hi, Ulrich,

I got from airlied two things:

a) if you use the very latest drivers from updates-testing, Xinerama should
hopefully (many more adjectives follow) work.
b) xrandr should work as well, could you try to add to your section with Driver
"radeon" this line
Option "SWcursor" "true"
? Does it help?

Comment 10 Matěj Cepl 2008-05-28 23:05:21 UTC
BTW, for more info radeon(4) is cool ;-)

Comment 11 Ulrich Drepper 2008-05-29 23:51:49 UTC
With the software cursor enabled I don't see the problem.

BTW: why should I use xinerama?  I though xrandr is the future?  It seems to
work fine.

Comment 12 Matěj Cepl 2008-05-30 10:11:21 UTC
(In reply to comment #11)
> BTW: why should I use xinerama?  I though xrandr is the future?  It seems to
> work fine.

No, you certainly don't have to. Airlied was just curious whether he has
actually fixed Xinerama for you ;). And yes, xrandr is the future (but
officially it hasn't come yet).

BTW, is not CLOSED yet, because hardware cursor should work (although I believe
the speed difference is negligible).

Comment 13 Bug Zapper 2009-06-10 01:13:26 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 WONTFIX if it remains open with a Fedora 
'version' of '9'.

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 prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 14 Ulrich Drepper 2009-06-10 02:15:29 UTC
I'm using SW Cursors for ages now.  The machine still runs F9.  Not sure whether any more recent release fixes things.  I'll file a new bug if I find a problem when I update the machine and still see problems.

Comment 15 Ulrich Drepper 2009-08-15 20:48:39 UTC
I've updated to F11 now and the problem still exists.  I'll use SWcursor again but perhaps this can be looked at.  I can run some limited testing if necessary.  The video card is the same as before.

Comment 16 Matěj Cepl 2009-11-05 18:19:45 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 17 Matěj Cepl 2010-02-26 12:19:52 UTC
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]

Comment 18 Matěj Cepl 2010-02-26 12:29:21 UTC
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Notice, that this is an automatically filed comment for all bugs with hanging NEEDINFO for longer time; it is possible by quirks of bugzilla, that some bugs are in this state even though you have attached the required information; please, make a comment to this bug ... that we should see correctly; I am sorry for the bothering you in such case.]

Comment 19 Ulrich Drepper 2010-02-27 03:30:59 UTC
In F12 I'm actually not using any xorg.conf anyway.  And Xinerama is not used, xrandr is.  I don't see the problem with this configuration which doesn't mean it is fixed.  But since I couldn't get Xinerama to work with F12 at all (the old config file produces no usable output, wrong resolution, flickering, green coloring...) I canot really verify this problem anymore.

Comment 20 Bug Zapper 2010-04-27 12:05:14 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 21 Bug Zapper 2010-06-28 10:38:26 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

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