Comment 74 for bug 615549

On 09/22/2010 04:10 PM, Jamie Krug wrote:
> Martin:
>
>> Crashes which happen during the running GNOME/KDE session are
>> unrelated to this.
>>
> Interesting. After sharing extensive results in bug #625239, it seemed
> quite clear that my issue related to the correct bug and that #625239
> was a duplicate of this one (and has been marked as such). Am I really
> dealing with a completely different bug still? If so, any tips would be
> incredibly appreciated. This has been a long frustrating road (i.e.,
> nice new loaded System76 Serval laptop w/Ubuntu 10.04, which is barely
> usable). Thanks in advance!
>
>
The way I see it it was well established that you had the same bug that
was fixed here _BUT_ you then went on to receive other crashes that I'm
not sure are related at all. I haven't checked but can you still
identify the same symptoms:

   X starts on shared tty with getty
   X tty has isig flag set (stty(1))
   X crashes on hitting Enter or 2 keys (and perhaps a few other) with a
SIGINT (Enter) or a rather obscure handler traceback?

All this should be established when the greeter screen is shown (change
to vt1)

Include

ps -ef | grep X
gdmtty="$(ps --no-heading -o tty -p $(pgrep X))"
stty -F "/dev/$gdmtty"
ps -f -t "$gdmtty"

To me the CRUCIAL determinant to this particular bug is that 'vt7' does
_not_ appear on the command line for X. If it does, you have a different
bug or it is fixed :)