1002:68b8 [Asus M5A97 EVO] Corrupt mouse cursor when using multimonitors

[clickwir]

I have 2 screens, sometimes one of the screens will have the cursor corrupt. Usually looks like the cursor is sliced vertically in about 3-5 slices and put back together in the wrong order. Moving the cursor between screens causes it to change from being fine on one screen to corrupt on the other. Affects not just the arrow, but others as well, such as move, resize and text select.

Using the default cursor theme, never changed it. Rebooting fixes it. Sometimes, very rarely (maybe 2 times over the past several years) it will fix on it's own. But those self fixes have only happened if I move the cursor between screens quickly just after it happens, if it's left to be corrupt for a moment or more... it will stay that way until a reboot.

Hard to say what causes it or when it happens. Maybe it's more likely to happen when moving a window between screens.

---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
DistUpgraded: 2013-10-05 23:33:35,358 DEBUG enabling apt cron job
DistroCodename: saucy
DistroRelease: Ubuntu 13.10
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates, 13.101, 3.11.0-14-generic, x86_64: installed
 fglrx-updates, 13.101, 3.11.0-15-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed
 virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:2543]
InstallationDate: Installed on 2013-04-28 (271 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
JockeyStatus:
 ERROR:root:Could not find any typelib for AppIndicator3
 kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use)
 kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
NonfreeKernelModules: fglrx
Package: xorg 1:7.7+1ubuntu6
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=cbbe4688-ab8c-43ac-b0d0-8d0c97d9e9ca ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Tags: saucy ubuntu
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-10-06 (111 days ago)
UserGroups:

dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Wed Jan 15 02:06:28 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.5-1ubuntu2~saucy1
xserver.video_driver: fglrx

[clickwir (clickwir)]

Tried changing cursor themes, same issue. Does not make a difference.

inxi -v1
System: Host: mach Kernel: 3.11.0-15-generic x86_64 (64 bit) Desktop: KDE 4.11.3 Distro: Ubuntu 13.10
CPU: Quad core AMD FX-4100 (-MCP-) clocked at 1400.00 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Juniper XT [Radeon HD 5770]
           X.Org: 1.14.5 driver: fglrx Resolution: 1920x1080@60.0hz, 1920x1080@60.0hz
           GLX Renderer: ATI Radeon HD 5700 Series GLX Version: 4.2.12337 - CPC 9.01
Drives: HDD Total Size: 1789.0GB (38.1% used)
Info: Processes: 240 Uptime: 8 days Memory: 4621.9/7931.3MB Client: Shell (bash) inxi: 1.9.12

[penalvch (penalvch)]

clickwir, thank you for reporting this and helping make Ubuntu better. Could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg REPLACE-WITH-BUG-NUMBER

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

apport information

[clickwir (clickwir)]

These logs are from my current installation. Since I don't know how to make it happen, I don't know how long I'd have to use the current development ISO before seeing the problem. Right now I can't be without my current setup for the days it might take to reproduce.

[Heikki Berg (heikki-berg)]

I have reproduced the same on Ubuntu 13.10 (KDE), Linuxmint 16 (KDE), and now also Linuxmint 16 (Cinnamon).

I will attach screenshot (using camera, where you can see the actual phenomenon), Screen capture DOES NOT capture the error, I will attach that to next comment. Maybe that helps to isolate it.

The error has always been on primary screen of a dual screen setup. Screen for extended desktop does not have this. Even a moderate googling shows that multiple persons are suffering from this. Usual suspects are xorg and/or fglrx/Catalyst drivers.

It takes a while for the mouse pointer corruption to manifest after a boot, and when it does, it comes when moving the mouse cursor from secondary screen to primary. Reboot resolves the issue.

Hardware:
Processor: Intel Core i7-4930K @ 3.40GHz (12 Cores), Motherboard: ASUS X79-DELUXE, Chipset: Intel Xeon E5 v2/Core, Memory: 16384MB, Disk: 2000GB Seagate ST2000DM001-1CH1 + 256GB Samsung SSD 840, Graphics: ASUS AMD Radeon R9 290 4096MB (1000/1250MHz), Audio: Realtek ALC1150, Monitor: ASUS PB278, Network: Intel 82579V Gigabit Connection + Broadcom BCM4352 802.11ac Wireless

Software:
OS: LinuxMint 16, Kernel: 3.11.0-12-generic (x86_64), Desktop: Cinnamon 2.0.14, Display Server: X Server 1.14.5, Display Driver: fglrx 13.35.5, OpenGL: 4.3.12780, Compiler: GCC 4.8 + Clang 3.3 (SVN 201389) + LLVM 3.3, File-System: ext4, Screen Resolution: 5120x1440

[Heikki Berg (heikki-berg)]

Screen capture of the window taken when mouse pointer corruption is visible on the screen. Screen capture suprisingly shows that everything is fine. Mouse pointer here is as it should be. However the photo of the previous comment was taken at the same time, without moving the mouse and clearly in the screen mouse pointer is corrupted.

[penalvch (penalvch)]

Heikki Berg, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Marc (marc2014)]

I've noticed an additional quirk. If I slowly move the cursor from the right screen to the left (after it has become cut-up as described by others), on the right screen the cursor is as it should be. As it gets within a few pixels of the left screen (but still fully on the right screen), the first slice starts to show up on the left screen. In other words, the cursor is partially rendered on the left screen before it should be and still fully rendered on the right screen. Very curious.

The distance between the first two slices of the cursor on the left screen is apparently precisely the distance of the uncorrupted cursor from the edge of the right screen when it starts to be rendered on the left screen too early. So it seems like there is some mismatch in the rendering locations and the internal rendering of the two monitors. Since the slicing occurs when switching between the monitors (from right to left for me), it seems like this is an artifact arising between the rendering location of the cursor as it is between monitors and the boundary between the screens.

Also note that all the alternate cursors (e.g. window resizing at corners) are similarly sliced up. So perhaps there is some kind of filter applied to the cursor image before rendering to the screen that is getting mangled/corrupted when switching between screens.

I also found a way to uncorrupt the cursor. In the Catalyst Control Center for the Radeon driver, going to "Digital Monitor (2)" (I have 2 monitors, might be different for other users), selecting the tab "properties", and checking "Reduce DVI frequency on high-resolution displays" (default unchecked) restored the cursor. This resets the right screen (with the working cursor!) and somehow restores the proper cursor on the left screen. When the cursor corrupts again, just cycle the toggle.

[penalvch (penalvch)]

Marc, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[per terje (perterje22)]

Bump.
Got Excacly the same issue. Followed a couple of threads and ended up here. I cant explain it better than you so i'll Copy your posts, Marc.

Followed.

Setup:
Kubuntu 13.10
AMD 14.3 beta
AMD Radeon HD R9 290x

3.11.0-18-generic
2x 30" dell. One one DVI and one on DP. 2560*1600x2

[penalvch (penalvch)]

per terje, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[per terje (perterje22)]

nwm. Solved.
I used the beta driver cause i had problems installing the stable one.

Install 13.12 from amd site.

amd-catalyst-13.12-linux-x86.x86_64.run --extract catalyst
Remove everything from this part to the end of the file within catalyst/common/lib/modules/fglrx/build_mod/kcl_acpi.c
FROM:
----------
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,6,3)
    if (!ACPI_SUCCESS(acpi_get_table_with_size(id, 0, &hdr, &tbl_size)))
#else
    tbl_size = 0x7fffffff;
    if (!ACPI_SUCCESS(acpi_get_table(id, 0, &hdr)))
......

-----------
TO:

-----------

#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,6,3)
    if (!ACPI_SUCCESS(acpi_get_table_with_size(id, 0, &hdr, &tbl_size)))
#else
    tbl_size = 0x7fffffff;
    if (!ACPI_SUCCESS(acpi_get_table(id, 0, &hdr)))
#endif
    {
        return KCL_ACPI_ERROR;
    }
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,9,1)
    ((acpi_tbl_table_handler)handler)(hdr);
#else
    ((acpi_table_handler)handler)(hdr);
#endif
    return KCL_ACPI_OK;
}
---------

Build.
sudo ./ati-installer.sh 13.251 --buildpkg Ubuntu/saucy

Go up one dir and dpkg them.

No more mouse glitches.
Have a nice one.

[Launchpad Janitor (janitor)]

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

[Ebanizmus (ya-x)]

Hello.
Confirming this.
Kubuntu 14.04.1, all updated. Using fglrx, AMD Radeon Redwood 5570.
Mouse pointer is corrupting many times per day, on the second screen it looks normal, but on first is corrupted. And some times it is long vertical line.

[penalvch (penalvch)]

Me (ya-x)Me (ya-x), thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jen Hart (allneuts)]

Radeon R9 390
fglrx-update (proprietary)

Corrupt on one screen sometimes. Reboot fixes for a time.
Possible link is Java applications.

[penalvch (penalvch)]

Jen Hart, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.