** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Thanks for the confirmation Sean and tankdriver - after a 16 hour
debugging session I was beginning to doubt my own findings!
I have a couple of ideas as to how this is happening, and where to look.
--
Xorg crashed at first login attempt
https://bugs.launchpad.net/bugs/532047
You received this b
I can say the following:
- It does not matter what password (length, strength) was set at install.
- When I enter the number 2, X crashes.
- It does not matter where (at what position) in the password the number 2 is
pressed.
- (this bug is not in Kubuntu)
--
Xorg crashed at first login attempt
Lovely, by that I mean I can confirm that with the '2', I experimented
with valid and invalid passwords, the problem is only happening with
the number 2 in the 6th poition of my password.
My crash happens as I type the 2, don't need to hit enter.
If the password is not valid one, then it does not
Further support for the supposition that another process is waiting for
input events from the keyboard: using the accessible on-screen keyboard
it is possible to log-in first time.
Putting together the keys that cause the reset with those that are
ignored, it appears that whatever is listening to
I've been progressively disabling the input devices to discover if one
of them may be the culprit via "/lib/udev/rules.d/65-xorg-evdev.rules"
until everything but the GlidePad was disabled:
$ egrep '(Adding input device|PreInit)' /var/log/Xorg.0.log
(II) config/udev: Adding input device "AlpsPS/2
So as not to lose this possibly useful snippet: If my password contains
a numeral the crash happens as soon as that numeral is typed; otherwise
the crash happens when I press Enter. E.g "my2pennies4" causes the crash
when I press "2" whereas "letmeinnow" doesn't cause a crash until I
press Enter.
I think this theory has some legs. I had noticed some apparently random
characters showing up on VT7 after stopping gdm manually during
debugging.
I've now restarted the PC several times, not touched the keyboard until
the gdm log-in screen appears. Select the user with the mouse and then
begin ty
This appears to be caused by stty calls in the init scripts that reset
the isig flag on the current VT, which means the VT gets a SIGQUIT when
Enter is pressed. I'm working on trying to confirm this scenario is the
cause.
References:
http://www.mail-archive.com/x...@lists.freedesktop.org/msg07800
** Tags added: crash
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
Xorg crashed at first login attempt
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
Xorg crashed at first login attempt
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40181780/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40181781/Dependencies.txt
** Attachment added: "GdmLog.txt"
http://launchpadlibrarian.net/40181782/GdmLog.txt
** Attachment ad
12 matches
Mail list logo
