Occassional mouse cursor corruption on primary display

[Joe Barnett]

I often get into the state where the cursor on my internal laptop display (1920x1080 resolution) gets corrupted into a single-pixel wide vertical dotted bar (see approximate center of attached screenshot), but the mouse cursor on my external display (1920x1200 resolution) is fine.

alternate cursors (window resize handles/text cursor, etc) either display the same vertical bar, stretch it out a few extra pixels, or cause the cursor to disappear entirely.

gnome-screenshot captures that include the cursor _do_ appear correct, but not sure how much of that is screenshot-capturing-cursor-emulation type code.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-ati 1:6.14.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
Date: Fri Jul 22 11:40:36 2011
DistUpgraded: Log time: 2011-07-13 10:07:59.371965
DistroCodename: oneiric
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 ATI Technologies Inc Broadway PRO [Mobility Radeon HD 5800 Series] [1002:68a1] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1522]
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
MachineType: Hewlett-Packard HP ENVY 15 Notebook PC
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-5-generic root=UUID=639dc488-e095-42a4-8c1f-ffb1a9299e1c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-ati
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (8 days ago)
dmi.bios.date: 04/23/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1522
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 36.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd04/23/2010:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr048F110000241920001530000:rvnHewlett-Packard:rn1522:rvr36.34:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP ENVY 15 Notebook PC
dmi.product.version: 048F110000241920001530000
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.5.0-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11~1-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11~1-0ubuntu4
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.2-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Bryce Harrington (bryce)]

Hi Joe,

Are you still reproducing this problem with the latest oneiric bits?

Not sure what might be causing it; I'm thinking this issue should be forwarded upstream.

[Joe Barnett (thejoe)]

Actually haven't seen this in a while; maybe has been fixed?

[Bryce Harrington (bryce)]

It's quite likely; I'll go ahead and close it, but feel free to reopen it if you see it occur again.

[Joe Barnett (thejoe)]

getting this again today.

[Joe Barnett (thejoe)]

...although it fixed itself this time!?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryce Harrington (bryce)]

Hey thejoe,

Hi, thanks for reporting this issue during the development period of
Ubuntu.

I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?

Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?

[Joe Barnett (thejoe)]

I'm ok with closing it; saw it once on 2011-10-10, and not since... will reopen when/if it comes back

[Jessica Mulein (jessica-mulein)]

I'm running Ubuntu 10.04 LTS with an ATI Radeon HD 5775 and 3 heads. Primary is 1920x1080 and the other two are 1280x1024. The primary screen has a corrupted cursor while the others are fine. The cursor on the primary has kind of a shadow copy and there's a several pixel line ripped out of the middle.

[Wong Yong Jie (yjwong)]

I'm on Ubuntu 11.10 with ATI Mobility Radeon HD 4670, got this issue today. Laptop's display is 1366x768, extended display is 1280x1024. Both screens have the same corrupted cursor and the pattern changes according to the color on which the cursor is pointed at.

[David Megginson (david-megginson)]

This bug affects me as well. Sometimes moving the pointer gently to the right side of my primary display restores the pointer completely, and sometimes it restores it to a slight scrambled version.

I also have a second, probably-related problem, where the system gets confused and compresses the mouse movement to about 30% of the screen width in my left (secondary) monitor. Neither happens 100% predictably. They're more likely after the secondary monitor (HDMI) has been unplugged and plugged back in, but can happen without that, too.

[Nikolaus Rath (nikratio)]

Bryce, why did you set this to "Fix Released"? The problem is still experienced by multiple users.

[Vertago1 (vertago1)]

This affects me on both fglrx, fglrx-updates, and the latest driver from AMD (as of today 2012-09-26). I have seen it since I build this computer with AMD cards. It only shows up on occasion and is hard to reproduce. I am using two Radeon HD5700 cards and Kubuntu 64bit 12.04. I am using two monitors, the problem only shows up on the primary display.

Rebooting clears the problem until it appears again.