invisible mouse pointer with Intel 855 graphic chip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
I have an Inspiron 700m which uses the Intel 855 graphical chip. Whenever I start the computer, the mouse pointer is invisible. I know the pointer is there because I can still click things if I get the pointer to the right locations. (By the way, this bug is exactly the same as Bug #614176, even the workaround. The newest updates, however, did not resolve the issue for me.) There are quite a few people reporting the problem on ubuntu forum, and apparently Stefan Glasenhardt (http://
Workaround: after a suspend/resume cycle, the pointer will be back.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'SigmaTel STAC9750,51'
Components : 'AC97a:83847650'
Controls : 33
Simple ctrls : 22
Date: Sat Oct 30 23:17:27 2010
HibernationDevice: RESUME=
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 700m
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: root=UUID=
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UserAsoundrc:
pcm.bluetooth {
type bluetooth
device 00:13:17:72:3E:A4
profile “hifi”
}
WpaSupplicantLog:
dmi.bios.date: 03/20/06
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: A07
dmi.board.name: 0RC359
dmi.board.vendor: DELL SYSTEM
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Inspiron 700m
dmi.product.
dmi.sys.vendor: Dell Inc.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
fz, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace- with-bug- number>
Also, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: testing
needs-upstream-
This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: testing
needs-upstream-
If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: unable- to-test- upstream unable- to-test- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
Please let us know your results. Thank you for your understanding.
Helpful Bug Reporting Tips: /help.ubuntu. com/community/ ReportingBugs
https:/