Bug 628217

Summary: Mouse cursor not visible
Product: [Fedora] Fedora Reporter: Łukasz Jernaś <deejay1>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: ajax, awilliam, luya, mcepl, rderooy, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.35.6-39.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-30 23:16:39 UTC Type: ---
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
Xorg.).log
none
lsmod output
none
lspci output
none
dmesg output
none
messages
none
Xorg.0.log
none
Xorg.0.log from LT20 tablet laptop none

Description Łukasz Jernaś 2010-08-28 16:50:25 UTC
Created attachment 441708 [details]
Xorg.).log

After installing F14 alpha and doing yum update and a subsequent reboot, the mouse cursor isn't visible anymore although when I move the mouse the tooltips appear and clicking works. I'm using the built in touchpad on a Toshiba Sattelite L10. I'm using a stock X11 config.
Logs attached

Comment 1 Łukasz Jernaś 2010-08-28 16:51:33 UTC
Created attachment 441710 [details]
lsmod output

Comment 2 Łukasz Jernaś 2010-08-28 16:52:10 UTC
Created attachment 441712 [details]
lspci output

Comment 3 Łukasz Jernaś 2010-08-28 16:54:23 UTC
Installed X.org packages:
xorg-x11-drv-wacom-0.10.8-1.20100726.fc14.i686
xorg-x11-drv-synaptics-1.2.99.1-3.20100617.fc14.i686
xorg-x11-drv-neomagic-1.2.5-1.fc14.i686
xorg-x11-drv-ati-6.13.1-0.2.20100705git37b348059.fc14.i686
xorg-x11-drv-void-1.3.0-6.fc14.i686
xorg-x11-drv-acecad-1.4.0-4.fc14.i686
xorg-x11-server-utils-7.4-19.fc14.i686
xorg-x11-drv-vmmouse-12.6.9-5.fc14.i686
xorg-x11-drv-glint-1.2.4-3.fc14.i686
xorg-x11-drv-intel-2.12.0-4.fc14.i686
xorg-x11-drv-savage-2.3.1-3.fc14.i686
xorg-x11-drv-mga-1.4.11-3.fc14.i686
xorg-x11-drv-i740-1.3.2-3.fc14.i686
xorg-x11-proto-devel-7.4-37.fc14.noarch
xorg-x11-font-utils-7.4-2.fc14.i686
xorg-x11-drv-r128-6.8.1-4.fc14.i686
xorg-x11-drv-ast-0.89.9-1.fc12.i686
xorg-x11-drv-elographics-1.2.4-2.fc14.i686
xorg-x11-drv-tdfx-1.4.3-3.fc14.i686
xorg-x11-drv-nouveau-0.0.16-9.20100615gitdb98ad2.fc14.i686
xorg-x11-drv-vmware-11.0.1-1.fc14.i686
xorg-x11-drv-s3virge-1.10.4-3.fc14.i686
xorg-x11-drv-openchrome-0.2.904-8.fc14.i686
xorg-x11-drv-sisusb-0.9.4-1.fc14.i686
xorg-x11-drv-apm-1.2.3-1.fc14.i686
xorg-x11-drv-cirrus-1.3.2-3.fc14.i686
xorg-x11-drivers-7.4-1.fc14.i686
xorg-x11-xauth-1.0.2-7.fc12.i686
xorg-x11-xinit-1.0.9-16.fc14.i686
xorg-x11-utils-7.4-10.fc14.i686
xorg-x11-drv-keyboard-1.4.0-5.fc14.i686
xorg-x11-drv-mach64-6.8.2-3.fc14.i686
xorg-x11-drv-fbdev-0.4.1-4.fc14.i686
xorg-x11-drv-vesa-2.3.0-1.fc14.i686
xorg-x11-drv-geode-2.11.4.1-4.fc14.i686
xorg-x11-drv-penmount-1.4.1-1.fc14.i686
xorg-x11-drv-i128-1.3.3-3.fc14.i686
xorg-x11-drv-qxl-0.0.12-2.fc14.i686
xorg-x11-drv-evdev-2.4.0-3.20100406.fc14.i686
xorg-x11-drv-mutouch-1.2.1-7.fc14.i686
xorg-x11-drv-voodoo-1.2.4-1.fc14.i686
xorg-x11-server-Xorg-1.8.99.906-2.fc14.i686
xorg-x11-drv-rendition-4.2.4-1.fc14.i686
xorg-x11-drv-mouse-1.5.0-5.fc14.i686
xorg-x11-drv-nv-2.1.15-6.fc14.i686
xorg-x11-drv-v4l-0.2.0-5.fc14.1.i686
xorg-x11-drv-sis-0.10.3-1.fc14.i686
xorg-x11-drv-siliconmotion-1.7.3-4.20100122.fc14.i686
xorg-x11-server-common-1.8.99.906-2.fc14.i686
xorg-x11-xkb-utils-7.4-8.fc14.i686
xorg-x11-drv-trident-1.3.4-1.fc14.i686
xorg-x11-drv-hyperpen-1.3.0-5.fc14.i686
xorg-x11-drv-aiptek-1.3.0-4.fc14.i686
xorg-x11-drv-dummy-0.3.4-1.fc14.i686
xorg-x11-drv-fpit-1.3.0-11.fc14.i686

Comment 4 Matěj Cepl 2010-08-31 11:16:31 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 5 Łukasz Jernaś 2010-08-31 16:03:04 UTC
Created attachment 442227 [details]
dmesg output

Comment 6 Łukasz Jernaś 2010-08-31 16:05:00 UTC
Created attachment 442228 [details]
messages

Comment 7 Łukasz Jernaś 2010-08-31 16:05:40 UTC
Created attachment 442229 [details]
Xorg.0.log

Comment 8 Łukasz Jernaś 2010-08-31 16:06:38 UTC
Requested files should be attached. I do not have an xorg.conf file in /etc/X11.

Comment 9 Luya Tshimbalanga 2010-09-18 18:22:21 UTC
Created attachment 448217 [details]
Xorg.0.log from LT20 tablet laptop

I have the same problem after using preupgrade from F13 to F14. I wonder if there is a regression related to intel driver or kernel.

Comment 10 Luya Tshimbalanga 2010-09-18 22:53:28 UTC
After testing with one older kernel (2.6.34) from Fedora 13, I can confirm the bug is related to the kernel (2.6.35). That is a sign of regression.

Comment 11 Łukasz Jernaś 2010-09-19 14:08:07 UTC
I've booted up the machine today and behold, I have my cursor back! 

[deejay1@betty ~]$ rpm -qa kernel*
kernel-PAE-2.6.35-0.57.rc6.git1.fc14.i686
kernel-headers-2.6.35.4-12.fc14.i686
kernel-PAE-2.6.35.4-12.fc14.i686
kernel-PAE-2.6.35.2-9.fc14.i686
[deejay1@betty ~]$ uname -a
Linux betty.foo.bar 2.6.35.4-12.fc14.i686.PAE #1 SMP Fri Aug 27 07:47:26 UTC 2010 i686 i686 i386 GNU/Linux

Comment 12 Łukasz Jernaś 2010-09-19 14:22:25 UTC
Ah well, now it's gone after another reboot…

Comment 13 Luya Tshimbalanga 2010-09-28 08:26:22 UTC
Kernel 2.6.35.6-34.fc14.i686 from koji fixes issue related to visibility of mouse cursor.

Comment 14 Łukasz Jernaś 2010-09-28 13:00:45 UTC
Confirming that it works with that kernel, even after a few reboots.

Comment 15 Adam Williamson 2010-10-07 18:32:43 UTC
ok, triaged, assigning to appropriate driver, we can close this when a kernel -34 or later is submitted as an update.

Comment 16 Robert de Rooy 2010-10-08 07:25:06 UTC
*** Bug 639250 has been marked as a duplicate of this bug. ***

Comment 17 Adam Williamson 2010-10-08 19:15:06 UTC
-39 has now been submitted as an update:

https://admin.fedoraproject.org/updates/kernel-2.6.35.6-39.fc14

Comment 18 Fedora Update System 2010-10-08 19:49:58 UTC
kernel-2.6.35.6-39.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/kernel-2.6.35.6-39.fc14

Comment 19 Fedora Update System 2010-10-09 03:31:59 UTC
kernel-2.6.35.6-39.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.