mouse stops working when switching to different X vt

[Markus Kienast]

Binary package hint: xserver-xorg

When I am switching users I am experiencing problems with my mouse:
This applies to feisty as well as gutsy.

1) I start a new gdm login via gnome.
2) After login, my mouse does not work.
3) I have to switch back to the previous VT and back again to activate the mouse.

The mouse sometimes freezes again, when I switch back and forth through the VTs. Occasionally, when I log out the second session and return to the initial one, the mouse speed doubles.

I am running a standard installation on feisty with nvidia proprietary driver. Same for gutsy.

There is another AIGLX related bug related to fast-user-switching and one UI bug that is worth getting attention. I will file them separately but reference them here as resolving them is equally important to make fast-user-switching a pleasant bug-free experience.

[Markus Kienast (elias1884)]

Other fast-user-switching bugs that need attention:
bug #134482 VT switching to locked AIGLX session shows nothing but white screen.
bug #134486 Gnome screen unlock should also show already opened sessions.

[Pascal De Vuyst (pascal-devuyst)]

Thanks for your bug report, more information is needed.

Do you have a laptop or desktop?
Please provide the minimal information described here: https://wiki.ubuntu.com/DebuggingMouseDetection.

[Carey Underwood (cwillu)]

Looks like a dup of Bug #134982 ("Mouse pointer freezes after opening up a new gdm login")

[Sitsofe Wheeler (sitsofe)]

elias:
Could you post the output of
lspci -nn
?

[Sitsofe Wheeler (sitsofe)]

(Probably a duplicate of Bug #88152 )

[Markus Kienast (elias1884)]

On Tue, 2007-08-28 at 22:22 +0000, Sitsofe Wheeler wrote:
> elias:
> Could you post the output of
> lspci -nn
> ?
>

lspci -nn from Feisty

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03)
00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03)
00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03)
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV43 [GeForce Go 6200 TurboCache] [10de:0168] (rev a1)
06:05.0 CardBus bridge [0607]: Texas Instruments PCI7420 CardBus Controller [104c:ac8e]
06:05.2 FireWire (IEEE 1394) [0c00]: Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller [104c:802e]
06:05.3 Mass storage controller [0180]: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller [104c:ac8f]
06:08.0 Ethernet controller [0200]: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile [8086:1068] (rev 03)
06:0b.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG Network Connection [8086:4220] (rev 05)

[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!

[Timo Aaltonen (tjaalton)]

elias: not a bad idea.. you could file a bug against launchpad and request that feature.

[Sitsofe Wheeler (sitsofe)]

elias:
I wonder who originally reported the wishlist item Bug #3382...

Let me apologise for asking for the same piece of information over and over again. I often don't twig that it is the same hardware on different bugs and since hardware information often doesn't turn up in a quick scan it is asked for again...

[Markus Kienast (elias1884)]

On Wed, 2007-08-29 at 10:21 +0000, Timo Aaltonen wrote:
> elias: not a bad idea.. you could file a bug against launchpad and
> request that feature.
>

https://bugs.launchpad.net/launchpad/+bug/135542

[Markus Kienast (elias1884)]

On Wed, 2007-08-29 at 10:54 +0000, Sitsofe Wheeler wrote:
> elias:
> I wonder who originally reported the wishlist item Bug #3382...
>
> Let me apologise for asking for the same piece of information over and
> over again. I often don't twig that it is the same hardware on different
> bugs and since hardware information often doesn't turn up in a quick
> scan it is asked for again...
>

Did not mean you asked for it repeatedly, but that I certainly have
submitted all that information more than once to launchpad (in different
bugs). So wouldn't it make sense to do what a programmer would do, to
have one central variable for that or a function or class if you like.
One central collection of my HW info, I could simply refer to?

I could of course also refer to the bug reports where I have already
pasted the information, but that would in turn make things more
complicated for you.

So my best bet is to make launchpad aware of my Hardware information.

[Sitsofe Wheeler (sitsofe)]

elias:
Does the problem subside if you aren't using AIGLX?

[Markus Kienast (elias1884)]

On Wed, 2007-08-29 at 11:57 +0000, Sitsofe Wheeler wrote:
> elias:
> Does the problem subside if you aren't using AIGLX?
>

Well, AIGLX extension is enabled by default in Feisty, but I am actually
not using it (no beryl or compiz running).

[Sitsofe Wheeler (sitsofe)]

elias:
I worded my question poorly. Does disabling desktop effects on Gutsy and using compiz allow VT switching to work?

[Sitsofe Wheeler (sitsofe)]

Gah, that should have been "and using metacity".

[Markus Kienast (elias1884)]

On Wed, 2007-08-29 at 22:14 +0000, Sitsofe Wheeler wrote:
> elias:
> I worded my question poorly. Does disabling desktop effects on Gutsy and using compiz allow VT switching to work?
>

No, this bug is unrelated to compiz. I am not using compiz on Feisty but
have the same problems here.

[Markus Kienast (elias1884)]

On Wed, 2007-08-29 at 22:14 +0000, Sitsofe Wheeler wrote:
> Gah, that should have been "and using metacity".
>

Same for Gutsy, the bug applies whether desktop effects are enabled or
not.

[Sitsofe Wheeler (sitsofe)]

Setting status back to new as reporter has answered all questions.

[Pascal De Vuyst (pascal-devuyst)]

elias,
Do you have a laptop? Is this the same issue as described in bug #68370 ?

[Markus Kienast (elias1884)]

Yes I have a laptop. And right it seems to be the same issue. My bad, I generalized this bug to appear with all "mice" while actually I did not test this with my USB mouse. I can only confirm the problem occurring with my Synaptics touchpad. Please let me know if you want me to upload any xorg log files etc. to the other bug?

[Pascal De Vuyst (pascal-devuyst)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #68370, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find.