nvidia being loaded automatically on an intel video machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
1. Description: Ubuntu lucid (development branch)
Release: 10.04
2. I have an intel video card. I don't know why anything nvidia would be running; I haven't loaded it. This appears to have been done automatically somehow. I don't have nvidia packages loaded. The only thing nvidia that gets reported by 'dpkg -l' is 'nvidia-
3. I expected nothing to happen.
4. This was reported by the Gnome crash applet.
ProblemType: Crash
Architecture: i386
Date: Sat Mar 6 16:42:14 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
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 Computer Corporation Inspiron 1150
Package: xserver-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
3.3V 32-bit PC Card
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcVersionSign
SourcePackage: nvidia-
Uname: Linux 2.6.32-14-generic i686
UserGroups:
dmi.bios.date: 06/05/2005
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A07
dmi.board.name: 0F3553
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: Inspiron 1150
dmi.sys.vendor: Dell Computer Corporation
system:
distro: Ubuntu
codename: lucidarchitecture: i686kernel: 2.6.32-14-generic
Most likely, you either installed it on accident or ran a script that installed it. This is not something which happens automatically. If it were, we'd be getting a LOT more reports about it.
I could be wrong though. If you can identify a specific set of steps to reproduce the issue, please provide them and reopen the bug report.