[jaunty + karmic] nvidia, artifacts on screen wher shutting down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-180 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nvidia-glx-185
Package: nvidia-glx-185 (173 and 180 also)
Release: 9.04, 9.10 Alpha 4 (32b)
Package version: 185.18.36-0ubuntu1
Expected result: clean shutdown with clear screen
Actual result: messy artifacts on the screen for ~ 1-10 seconds (see attachment)
GPU: Nvidia Quadro NVS 140M
Progress bar with ubuntu logo descends to zero and then I can see the bug. All other distros are ok (Fedora 11, openSUSE, Arch).
I hope "ubuntu-bug" will attach all necessary files. If not, just ask me for what you need.
ProblemType: Bug
Architecture: i386
Date: Sun Aug 23 23:40:42 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 8918DEG
NonfreeKernelMo
Package: nvidia-glx-185 185.18.36-0ubuntu1
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.5-1ubuntu1
libdrm2 2.4.12-1ubuntu1
xserver-
xserver-
SourcePackage: nvidia-
Uname: Linux 2.6.31-6-generic i686
dmi.bios.date: 10/20/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7KETC6WW (2.26 )
dmi.board.name: 8918DEG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 8918DEG
dmi.product.
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-6-generic
[lspci]
01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro NVS 140M [10de:0429] (rev a1)
Subsystem: Lenovo Device [17aa:20d8]
Well.. is this bug publicly visible? I'm new here so I don't know how it works, but it seems that this is common problem with Ubuntu+nVidia mobile (acording to ubuntuforums and launchpad).
#85451 looks pretty similar to this one.
#377120 is the same issue, but there is no solution or activity.