Logged out when typing 2 or @

[Martin Karlsson]

I get logged out to the GDM screen when typing in the password to my wireless network. It's always with the same character, namely @ (or as it turned out, it's sufficient to press the key 2). After I log in again I can successfully enter the password.

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Feb 16 11:33:16 2010
DistroRelease: Ubuntu 10.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100215)
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.4 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.8~rc2-0ubuntu1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: network-manager-applet
Uname: Linux 2.6.32-13-generic x86_64
WifiSyslog:

[Martin Karlsson (foh1981)]

I discovered that it doesn't matter where I type the character, so i choose gnome-desktop as package instead

[Martin Karlsson (foh1981)]

I tried entering the @ character in the adress bar in Firefox and I got logged out then as well. Appart from that I'm also having trouble with this bug, don't know if they are related somehow: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/519505

[Martin Karlsson (foh1981)]

Funny enough the Enter hang bug "disappears" after I've logged in again.

I've tried logging in, hitting Enter and the desktop hangs. But if I log in, hit @ and get logged out, then log in again the desktop doesn't seem to hang when hitting Enter.

[Ramón Rocha (ramon.rocha)]

I also encountered this bug in Lucid. It appears to consistently happen for me when hitting the number 2 key on the keyboard.

Moreover, when two monitors are connected, instead of my session ending and getting returned to the login screen, both of my monitors shutoff and the keyboard becomes unresponsive.

Martin, before doing the logout/login workaround, do you see graphical corruption at the top of your screen that gets worse the more you type?

[Martin Karlsson (foh1981)]

Yes, I do. The graphics corruption is present with the open source nVidia driver, but not with the proprietary driver. The corruption is present all the time with the open source driver, but in much lesser degree before the system hangs (it's basically just a couple of black pixels at the top most line of pixels). When the system hangs and I type something, I get what you describe at the top of the screen.

[Martin Karlsson (foh1981)]

No, you're right, it gets worse all the time while typing. As I remembered the corruption only worsened when the system froze, but that's not the case. And also, as you say, it's the 2 key that's the problem and not the @. I'll change bug title accordingly :)

[Alex Valavanis (valavanisalex)]

This is pretty similar to bug #519213. If I press the 2 key (or SHIFT+2), when the gdm password field has focus, then X restarts.

[Ramón Rocha (ramon.rocha)]

It may be the same bug. I had autologin enabled so it bypassed the initial password prompt in my case.

[Martin Karlsson (foh1981)]

Must be the same, should probably be marked as duplicate but I'm leaving it as it is for now (that way it has a better chance to show up in search results).

[Alex Valavanis (valavanisalex)]

@Martin Karlsson
Do you have autologin enabled too?

[Andreas Noteng (andreas-noteng)]

For me this happens only with proprietary driver, not with nouveau, have not tested the nv driver.

[Martin Karlsson (foh1981)]

@Alex
I've tried both with autologin and without. My description in the bug report is with autologin enabled, but after your comments I tried without too. It doesn't matter for me: hitting 2 on the GDM screen restarts the X server. If I reboot, log in and then hit 2 I get logged out. Same as for you I guess?

It only happen once after each reboot, just as the "Enter hang bug" linked to earlier.

Also it doesn't matter if I'm using proprietary driver or not.

[Graziano (graziano-giuliani-gmail)]

Gosh.... I have to press the 2 key in my password and I have to login always twice... Also for me this is the closest description of the behaviour I have managed to find.

Environment: Ubuntu lucid, NVIDIA OR NV drivers.
Signs: Screen shows "distorted" pixels on top left.

IF I see a non perfect screen (some key sequence seems to be sent to terminal) and I press the key "2", the X server restarts. No strange signs on logs (ending on request).
Second time I always get a perfect gdm login screen and I can login successfully. Never happens again, even if I logout and login again.

SEEMS some spurious characters coming out from startup are pushed to tty7, and "request" a gdm restart AFTER the key "2" pression.
This is mostly an annoyance for me, but for sure can hide something more serious.

[Graziano (graziano-giuliani-gmail)]

One note: I do NOT have autologin enabled, and I am affected.

[papukaija (papukaija)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting with Lucid, Ubuntu is transitioning to using the -nouveau video driver by default instead of -nv. The reason for this change is because upstream development for the -nv driver has been quite slow. We hope bugs will get fixed faster with -nouveau as well.

Because of this, I'm closing this bug report at this time. I'm marking it incomplete because what you describe is probably a valid issue, but we do not have intentions to work on it in Ubuntu. If you would still like to see this issue investigated, I would encourage you to file it upstream.

[papukaija (papukaija)]

Please mark this bug as won't fix (only the -nv part).

[Chris Halse Rogers (raof)]

I suspect that you're seeing a strange manifestation of bug #522692. Can you check if removing plymouth fixes your problem?

[Graziano (graziano-giuliani-gmail)]

Chris, seems that You have correctly tracked down the problem. Removing Plymouth fixes the problem for me. I am +1 to mark this bug as duplicate of bug #522692 with different symptoms.

[Martin Karlsson (foh1981)]

Same here, removing plymouth fixed the problem. I'm leaving it to others to change package accordingly, mark as duplicate etc. I'm not sure what's the correct way to do all that :)

[owen.c (owen-c93)]

My scroll lock is activated when I press "r". Anyone else?