ubuntu-x-swat team mailing list archive

["John S. Gruber" <JohnSGruber@xxxxxxxxx>]

I'm an Ubuntu amateur, so believe what Steve says over what I say. He's
no amateur.

I don't think the message "requirement "user ingroup nopasswdlogin" not
met by user "bilal" " is a problem. I see from the forum post
http://ubuntuforums.org/showthread.php?t=819198 that this is a
requirement that a userid like "guest" might meet so that no password is
required for that particular userid. Userid's requiring passwords should
not be in this group. If I'm right, and if the userid bilal and oem
require passwords, that particular message in the log would be expected.

The reason I suggested in now closed duplicate bug #529230 that someone
look in the auth file was to look for evidence that the getty program ,
responsible for getting people logged in on virtual consoles 1-6, was
active seeing keystrokes coming from the xsession and getting confused.
This only happens if x is started on tty1-tty6, as is happening to
Jamie. See Steve's comment 18 above.

This probably isn't happening to Bilal. His xorg.0.log.old has the X
crash and that log says it started on vt7. Andres says his crashing X is
starting on vt7.

I haven't gotten my head around dino99's report, but I don't think most
people who have had this problem have had a problem with authentication,
only with interference with x, either from plymouth (which should have
quit just before X started, if I'm correct), or from getty. In the case
of getty, I think the interference only crashes X after getty thinks,
mistakenly, that it has seen several login attempts and restarts. It
messes with the virtual terminal when it does that and that does in X
when you next press the 2 or enter key. That might be the reason for
Jamie's delay before the crash.

-- 
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.