1002:674a [HP Z620 Workstation] Corrupted mouse cursor on one of the screens

[Balazs Kelemen]

Corrupted mouse cursor on one of the screens.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
CurrentDesktop: KDE
Date: Thu Dec 11 12:56:37 2014
DistUpgraded: 2014-08-28 15:51:15,355 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: kubuntu
DkmsStatus:
 fglrx-updates, 13.350.1, 3.13.0-36-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
 virtualbox-guest, 4.3.10, 3.13.0-36-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks GL [FirePro V3900] [1002:674a] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:0122]
InstallationDate: Installed on 2013-10-22 (414 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
LightdmGreeterLog:
 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession
LightdmGreeterLogOld:
 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession
MachineType: Hewlett-Packard HP Z620 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=6f44318e-b0cf-46d7-a4f7-882fcb7934b9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-08-28 (104 days ago)
dmi.bios.date: 05/09/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J61 v03.15
dmi.board.asset.tag: 2UA32613WN
dmi.board.name: 158A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 0.00
dmi.chassis.asset.tag: 2UA32613WN
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.15:bd05/09/2013:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z620 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Dec 5 11:24:22 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: fglrx

[Balazs Kelemen (balazskelemen99)]

Note that the screenshot from bug 360724 is exactly the same as I am experiencing.

[Balazs Kelemen (balazskelemen99)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
J61 v03.85
11/19/2014

[Balazs Kelemen (balazskelemen99)]

The bios update did not change anything unfortunately. As for what happened, if I understand the question correctly, as I said I experience pretty much the same as what is described in #360724. The bug is still present and occurs after booting at a random point, it can be an hour, a day, or several days. It only goes away after a restart.

[Balazs Kelemen (balazskelemen99)]

Apparently the last claim is not correct, restarting X also make it go away.

[penalvch (penalvch)]

Balazs Kelemen, to see if this is resolved in a later release, would it be possible for you to do an in-place upgrade to Utopic or reinstall with Vivid?

[Tynach (tynach2)]

I'm on 14.10 using an AMD Radeon R9 290X, and having the same issue. The fact that we're supposed to make new bug reports every time someone's hardware is slightly different or a new version of Ubuntu comes out is mildly infuriating, because it makes it seem as if there are fewer people with this issue than there really are. I've seen tons of bug reports with almost no activity, probably because people just went to nVidia and never bothered to check back here.

This problem seems to happen with all AMD display adapters when there are 2 or more monitors, with very few exceptions. I feel that studying those exceptions separately from when it *doesn't* work will be more helpful, because not working seems to be the norm.

If there is a 'central' bug report for this issue that hasn't been marked 'invalid' because it was started on an old version of Ubuntu, please point me to it. If you tell me to just make another bug report, please tell me why that will help in any way, shape, or form. Seriously. It's not helped the countless people so far, and the chances of it helping me seem nil.

[penalvch (penalvch)]

Tynach, bug reports are not done on a per symptom basis initially, but per hardware, and per original reporter. Hence, it's most helpful to developers if you file a new report via a terminal:
ubuntu-bug xorg

The rationale for this is fully covered in the following publicly available support articles:
https://wiki.ubuntu.com/X/Reporting
https://wiki.ubuntu.com/ReportingBugs

[Balazs Kelemen (balazskelemen99)]

I can't try updating because it is my work desktop and I need to use stable version and don't have time to experiment with this.

I went back to open source driver. Obviously the graphics performance and capabilities are poor but that's less of a problem for me.

What Tynach said, I cannot agree more. It is completely ridiculous to ask people to create new bug reports all the time. This is simply not how software development works, if you treat every goddamn occurrence of a problem in every goddamn environment separately you never gonna fix nothing.

[Tynach (tynach2)]

Christopher, it is unlikely that any automated tool is ever going to capture this bug any more than it already has. It is much more beneficial to find out why it might NOT happen, than why it DOES happen. What's more, is that it seems that this bug is in the proprietary driver upstream... So the most helpful thing we could do to get this fixed, is to show how many people are affected.

Because the current way of doing things does not in any way show how many people are affected, the current way of doing things will simply not help. It is utterly flawed, and those articles don't help to address this matter. For one thing, those articles are written with crashes and bad behavior within open source software in mind - neither of which is the case here.

[Launchpad Janitor (janitor)]

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