Comment 13 for bug 529230

Hi!

First of all, sorry for my bad english.

This happens only in computers in my laptops with NVidia GPU's...

Before some fixs, if i press Enter after inserting password, computer crash.
The solution was insert password click on log in button, and log out. After
i insert password again, i can log in pressing Enter with no crash.

With latest updates, when i press enter in first tentative, monitor turns
black, after that, monitor shows a bunch of rectangles in screen and back to
login screen.
I try login again and always work well after this.

I will pm you(with phone video), when beta release comes out and this last
problem still show up.

Good Job

2010/3/10 John S. Gruber <email address hidden>

> Henning:
>
> Thanks for the information. Does it crash the first time you type these
> keys or can you type them at first but later it crashes? If the second
> case could you post your Xorg.0.log from when it crashed (hopefully in
> Xorg.0.log.old)? In that case I'm wondering whether the crashing X
> session started on VT1 rather than VT7 as did Marc's and mine (noted in
> the beginning of the log).
>
> If it happens the first time you press a certain key in a session I
> think you might want LP# 532047.
>
> --
> X server crashes when enter key is pressed
> https://bugs.launchpad.net/bugs/529230
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “plymouth” package in Ubuntu: Confirmed
>
> Bug description:
> kosh@isis:~$ lsb_release -rd
> Description: Ubuntu lucid (development branch)
> Release: 10.04
> kosh@isis:~$ dpkg -l xserver-xorg-core | egrep -e ^i
> ii xserver-xorg-core 2:1.7.5-1ubuntu1
> Xorg X server - core server
>
> Sometimes the X server crashes when I press the enter key. It happens
> seldomly, so I can still work, but sometimes X will just die right when I
> press enter. This has happened in oocalc, mplayer and gnome-terminal, and
> the application does not receive the key press event (or has no time to act
> on it).
>
> I have attached my X server log which shows a backtrace:
>
> Backtrace:
> 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a2528]
> 1: /usr/bin/X (0x400000+0x6522d) [0x46522d]
> 2: /lib/libpthread.so.0 (0x7fe52032b000+0xf920) [0x7fe52033a920]
> 3: /lib/libc.so.6 (__select+0x13) [0x7fe51f0e4c53]
> 4: /usr/bin/X (WaitForSomething+0x1ba) [0x45f5fa]
> 5: /usr/bin/X (0x400000+0x308d2) [0x4308d2]
> 6: /usr/bin/X (0x400000+0x2614a) [0x42614a]
> 7: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fe51f024c4d]
> 8: /usr/bin/X (0x400000+0x25cf9) [0x425cf9]
>
> Caught signal 3 (Quit). Server aborting
>
> I first noticed this problem on February 21st, so after this upgrade:
>
> [UPGRADE] xserver-xorg-core 2:1.7.3.902-1ubuntu12 -> 2:1.7.5-1ubuntu1
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/529230/+subscribe
>