Bug 1132662

Summary: Mouse pointer disappears & is not recoverable
Product: [Fedora] Fedora Reporter: Jim Campbell <jim>
Component: kernelAssignee: Adam Jackson <ajax>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ajax, awilliam, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-07 03:17:40 UTC Type: Bug
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
dmesg-output
none
evtest-output
none
glxinfo-output
none
lspci-output
none
lsusb-output
none
uname-a-output
none
xorg-0-log
none
output of journalctl -b after booting with latest rawhide kernel none

Description Jim Campbell 2014-08-21 19:10:01 UTC
Created attachment 929325 [details]
dmesg-output

Description of problem:

On booting into the latest rawhide kernel, my mouse pointer disappears and is not recoverable. I've attempted workarounds as posted on the internet (e.g., switching into a virtual terminal, and then switching back to the gui), but no attempts actually resolve the problem.

After running into this problem on Rawhide, I switched back to Fedora 20, but still try out the Rawhide Kernel from Fedora 20 to see if this problem is fixed.

I do briefly see the mouse pointer in the transition between GDM and the desktop, but it is otherwise not present at all - not even as a ghost pointer which is there and can be used but just can't be seen.

Version-Release number of selected component (if applicable):

Linux localhost.localdomain 3.17.0-0.rc1.git1.1.fc22.x86_64 #1 SMP Wed Aug 20 14:00:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

This is the rawhide kernel, 3.17.0-0.rc1.git1.1.fc22.x86_64 


How reproducible:

Always

Steps to Reproduce:
1. Boot into the laptop
2. Notice that mouse pointer is not present

Actual results:

Same

Expected results:

Mouse pointer should be visible and functional.

Additional info:

See attached system info. This is on a Haswell Dell XPS 13 (2014).

Comment 1 Jim Campbell 2014-08-21 19:10:35 UTC
Created attachment 929326 [details]
evtest-output

Comment 2 Jim Campbell 2014-08-21 19:11:09 UTC
Created attachment 929327 [details]
glxinfo-output

Comment 3 Jim Campbell 2014-08-21 19:11:34 UTC
Created attachment 929328 [details]
lspci-output

Comment 4 Jim Campbell 2014-08-21 19:11:58 UTC
Created attachment 929329 [details]
lsusb-output

Comment 5 Jim Campbell 2014-08-21 19:12:26 UTC
Created attachment 929330 [details]
uname-a-output

Comment 6 Jim Campbell 2014-08-21 19:13:42 UTC
Created attachment 929331 [details]
xorg-0-log

Note that this log shows the Fedora 20 kernel. I wasn't able to see anything in the logs with regards to the Rawhide (3.17) kernel.

Comment 7 Jim Campbell 2014-08-21 19:16:23 UTC
I had attempted to run Rawhide because screen brightness and suspend-resume do not work on Fedora 20. Those issues appear to be resolved in the Rawhide kernel. However, this past week the "no mouse button" issue cropped up. I think it occurred with updates that I installed on Sunday or Monday evening, August 17th or 18th, 2014.

Thanks for your help!

Comment 8 Jim Campbell 2014-08-29 04:05:49 UTC
I have consistently reproduced this issue on both the kernel that was originally mentioned, on up through more recent kernels.

As of now, this problem still exists on kernel-3.17.0-0.rc2.git2.1.fc22.

Comment 9 Adam Williamson 2014-08-30 18:00:06 UTC
<j1mc> yes - my screen does have touch capability, and i'm using gnome-shell

Comment 10 Jim Campbell 2014-08-30 18:33:19 UTC
Created attachment 932982 [details]
output of journalctl -b after booting with latest rawhide kernel

current tested kernel version is 3.17.0-0.rc2.git3.1.fc22

Comment 11 Jim Campbell 2014-09-07 03:17:40 UTC
This issue appears to be fixed with an update to kernel 3.17.0-0.rc3.git3.1.fc22.x86_64.

I'm not sure what fixed it, so please let me know if you'd like more info (e.g., if you'd like me to re-run any of the tests that I ran previously).

Thanks.