[nvidia] VT switching to locked AIGLX session shows nothing but white screen.

[Markus Kienast]

Binary package hint: xorg

When I switch to a VT with active screen locking and compiz AIGLX running, I see nothing but a whiteish screen. When I move the mouse, I can see the cursor change if I am over the invisible password input field. I can also enter the pwd and the screen is unlocked as usual.

This concerns gutsy and I think to remember this happens in feisty as well, with both beryl and compiz.

I am using the nvidia proprietary driver.

[Sitsofe Wheeler (sitsofe)]

Thank you for your bug report.

elias:
Can you indicate which version of Ubuntu you are running along with what
lspci
indicates your VGA card to be?

[Sitsofe Wheeler (sitsofe)]

I have just noticed that the original comment mentioned gutsy. Punting from xorg -> linux-restricted-modules-2.6.22 as the binary driver is involved. Almost certainly a duplicate of Bug #88152 ...

[Sitsofe Wheeler (sitsofe)]

Could also be #134289 ... We would need to know which graphics card was involved and what
dpkg -l \*nvidia\* | grep -i ii
produced...

[Sitsofe Wheeler (sitsofe)]

elsias:
Can you add the output of running
lspci -nn
dpkg -l \*nvidia\* | grep -i ii
to this bug report?

[Sitsofe Wheeler (sitsofe)]

Resolving as a duplicate of Bug #134478 as these are different steps for generating the same issue (VT switching) and the reporter is the same in both cases.

[Markus Kienast (elias1884)]

On Fri, 2007-08-24 at 19:42 +0000, Sitsofe Wheeler wrote:
> Could also be #134289 ... We would need to know which graphics card was involved and what
> dpkg -l \*nvidia\* | grep -i ii
> produced...
>

Feisty:
ii nvidia-glx 1.0.9631+2.6.20.5-16.29 NVIDIA binary XFree86
4.x/X.Org driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel
module common files

[Markus Kienast (elias1884)]

the above lspci -nn is from feisty

[Markus Kienast (elias1884)]

Since again, I had to attach the same lspci file to several bugs, I want to make all devs and bug fixers aware of this bug https://bugs.launchpad.net/malone/+bug/3382

I find it is absolutely necessary to be able to attach hardware profiles to launchpad user accounts. I would then simply say, this happens on Feisty on my machine XY and you guys could immediately access the right record in the HW DB. Now you have to over and over again request us to send lspci outputs, lshw outputs, ....

Isn't it the purpose of programming to relieve us from things that we have to do over and over again in exactly the same way? Isn't that what computers are for, to do exactly these stupid always the same operations?

Please use your voice as bug fixers, as the people most annoyed by this, to get canonical to implement such a feature in launchpad!

[Pascal De Vuyst (pascal-devuyst)]

Bug #134478 has been marked as a duplicate of bug #68370.
This bug doesn't seem to be a duplicate of bug #68370, shouldn't we remove the duplicate mark?