Mouse cursor invisible at boot on i852GME

[Scott Testerman]

Binary package hint: xserver-xorg-video-intel

On cold boot with up to date Kubuntu Maverick, the mouse cursor is invisible at boot. Moving the mouse around the login screen reveals that it is still present and is merely invisible. Suspending the machine at the login screen and then resuming will make the cursor visible, and the cursor continues to work correctly through the rest of the session.

This behavior has changed since Maverick Alpha 2, when the cursor did work correctly at boot. The bug is similar to bug 475917 and bug 508697. It cannot be fixed by removing ~/.config/monitors.xml (because there isn't one). I am not using the nomodeset or i915.modeset=0 parameters because these were not previously required on Maverick.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1400x1050
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Sun Aug 8 20:29:15 2010
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog:
 Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /home/scott/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100701)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 07cc:0301 Carry Computer Eng., Co., Ltd 6-in-1 Card Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway Gateway M350WVN
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=c64ffa3b-49d7-4565-a4c7-8c5a32f54697 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 04/23/2004
dmi.bios.vendor: Gateway
dmi.bios.version: 34.01.00
dmi.board.name: Gateway M350WVN
dmi.board.vendor: Gateway
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: QCIPRC
dmi.modalias: dmi:bvnGateway:bvr34.01.00:bd04/23/2004:svnGateway:pnGatewayM350WVN:pvrRev1:rvnGateway:rnGatewayM350WVN:rvrRev1.0:cvnGateway:ct10:cvrQCIPRC:
dmi.product.name: Gateway M350WVN
dmi.product.version: Rev 1
dmi.sys.vendor: Gateway
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-14-generic

[ubu64 (santiago-beckenried)]

Yes this again related to the old kms 855GM problems

see also

for Lucid
http://glasen-hardt.de

and it is related to the transition from 2.6.35-12-generic to 2.6.35-15-generic

What is more worrying is the fact that that there are sporadic
mount errors on ext4 when resuming from suspend state which makes a reboot necessary.
So putting it into suspend is no workaround.

[Scott Testerman (scott-testerman)]

Hi Ubu64!

Thanks for the information about the mount errors on your system. Please note that you commented on a bug that had already been marked as a duplicate of another bug report, so your comment may go unnoticed. If you'd like to report additional findings about this bug, please comment at the main bug report, bug #614176.

Thanks for helping to make Ubuntu better!