Mouse Cursor Invisible

[Vindicator]

My first experience was while using kernel 3.9.21 which I upgraded to today.
I read about "gsettings set org.gnome.settings-daemon.plugins.cursor active false", but it didn't bring it back (I did not reboot).
Then I also read about CTRL-ALT-F1 -> F7 and it came back.

Then I built my own kernel 4.0, rebooted and straight away the mouse cursor was nowhere to be seen (don't remember if it was visible during login).
Right away I tried CTRL-ALT-F1 -> F7 and that did nothing. Luckily items will highlight when hovered over, so I got my browser up and also brought up the terminal to try gsettings again, but to no avail.
That's when I tried ubuntu-bug report and at the very last stage when I'm about to press "Send", the cursor shows up.

I went ahead and sent the report anyway in hopes that the capturing part of the report would show the visibility issue.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
Uname: Linux 4.0.0-040000-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jun 16 16:56:30 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:041e]
InstallationDate: Installed on 2015-06-04 (12 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.0-040000-generic root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: H97M-ITX/ac
dmi.board.vendor: ASRock
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.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr: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 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Jun 16 16:50:18 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.1-0ubuntu3

[Vindicator (vindicator)]

Ugh, I missed your message that was in the spam folder. Surprised I've gone this long without looking.

I was surprised to see there was a BIOS update, so I'll be taking care of that.

I actually just encountered the mouse issue again while watching a video. I also find that it'll also disappear when I move inside a terminal window, but I think it'll reappear when I click in the window. It did NOT reappear when I completely lost it while watching the video though.

I ran the dmidecode anyway just to see but got "/dev/mem: No such file or directory".

I'll get back at it when I wake up. I'm up way too late and am getting punchy.

[Vindicator (vindicator)]

I'm attaching a bug report for when there was no visible mouse cursor at the log in screen.
I switched to tty to create the bug report but forgot I originally reported the XOrg and instead did nautilus this time.

I DID update my BIOS to 1.70 and it is still happening. I'm finding it happen with greater frequency too, particularly at the log in screen.
The cursor will typically no appear until I first move the mouse, but there are times when it won't even appear when I do move it.
It's there, but just not visible, as I can click the cog wheel.

[Vindicator (vindicator)]

Same session as last comment/report but after I've logged in and the cursor is still invisible.

I'll try to remember to make a report with the XOrg package.
*Maybe a specific package/process can be suggested that I capture a report on.

[Vindicator (vindicator)]

So now it's looking to be a 100% of the time sort of issue considering that I just now rebooted my machine and the exact same sequence occurred.
The mouse wasn't visible at log in and didn't appear when logged in.
Only when I logged out did the mouse cursor appear.

[penalvch (penalvch)]

Vindicator, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Vindicator (vindicator)]

OK, so having updated the...
1) bios to:
  $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
  P1.70
  05/12/2015
2) kernel to (no errors in the build and install):
  $ uname -r
  4.1.1-040101-generic
... the effect is still in play.

I will say it is NOT 100% of the time anymore. I had done one more reboot BEFORE updating the kernel and it was OK. It was also OK the first time after I rebooted AFTER updating the kernel, however I just did another reboot and it happened again until I logged back out.

Adding tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.1.1-unstable

[penalvch (penalvch)]

Vindicator, could you please test the latest mainline kernel (4.2-rc1) and advise to the results?

[Vindicator (vindicator)]

4.2-rc1 was a COMPLETE failure.
It began with the build using "binary-perarch". I only added that because of the linux-cloud* and linux-tools* installation (which I figure probably isn't needed, but it's there). That isn't a big deal.

I cleaned and recompiled and installed just fine.

HOWEVER, boot was where the "complete" failure occurred.
I don't know how to get the log and submit a bug report for that (I'll research submission methods). I took some pictures with my phone.
At the end of the first trace, it said "Fixing recursive fault but reboot is needed!"

I'm also wondering what this "testing" is supposed to be doing. This is an issue that has been on the books for years if you were to search online for "(invisible OR disappearing) mouse (gnome OR linux OR ubuntu)".

[penalvch (penalvch)]

Vindicator, just to clarify, there should be no compiling required, as .deb files are already provided.

Despite this, as per the support article, you would install only three files:
1)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc1-unstable/linux-headers-4.2.0-040200rc1-generic_4.2.0-040200rc1.201507051635_amd64.deb

2)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc1-unstable/linux-headers-4.2.0-040200rc1_4.2.0-040200rc1.201507051635_all.deb

3)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc1-unstable/linux-image-4.2.0-040200rc1-generic_4.2.0-040200rc1.201507051635_amd64.deb

Is this what you did to get your results in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465862/comments/11 ?

[Vindicator (vindicator)]

For me, I DO need to compile because I have to adjust a module for my tv tuner and for my LAN.
I did install the 2 headers and 1 image file that I compiled (done for every kernel tested so far), not downloaded, but just to be thorough in the testing, I will d/l those files now and test them after forcing the removal of the failed one I compiled.

[Vindicator (vindicator)]

I was right about the kernel, even after removing what I compiled and installing the packages you linked to, the same boot failure occurred.

[Vindicator (vindicator)]

http://www.phoronix.com/scan.php?page=news_item&px=Early-Linux-4.2-Woes
DING DING DING! ^This is what I'm experiencing with 4.2.

[penalvch (penalvch)]

Vindicator, it is strongly recommended you file one bug report for your TV tuner, and one for your LAN device not working by default via a terminal:
ubuntu-bug linux

Having to WORKAROUND those issues makes trying to investigate the issue scoped to this report difficult.

[Vindicator (vindicator)]

I don't know if the tuner and LAN issues warrant a report since I think it may be by design.

The LAN issue was due to redacted code: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2
When adding the code back in, I am now able to WOL just fine as well as still Sleep with no problems.

The TV tuner, somewhat simply, didn't include a PID value in ./drivers/media/usb/au0828/au0828-cards.c, so I just duplicate the nearest VID/PID pair { USB_DEVICE(0x05e1, 0x0480) replacing 480 with my 400.
It isn't an exact match in functionality as a native driver in Windows because there is an LED on the device that remains lit, otherwise it works fine.

Do you think it would still be something to ubuntu-bug the specific modules that I have edited?

[Vindicator (vindicator)]

I'm going back to the 100% of the time issue.
I'm finding that the 100% occurs during boot when I switch to the "detailed output" part of the boot (ESC) instead of leaving it at the graphical mode.

It does NOT explain the disappearing mouse when I hover over a terminal window. The mouse would reappear if:
1) I move the mouse out of the terminal window or
2) I click in the terminal window.
The disappearing state is not 100% of the time and will get introduced at any point during the session.

It does NOT explain the disappearing mouse completely at unknown/random times. It is pretty rare, but can happen. I'm not sure if I had tried just logging out and back (like at the boot->login time) in when it happens at that time.