VIOLA! EUREKA! Commenting out the call to stty sane in
/etc/init.d/apache2 worked like magic for me I know the problem now!
It doesn't affect Plymouth or X or GDM or Linux or Upstart, but Apache!
I am going to propose a patch.
** Also affects: apache2 (Ubuntu)
Importance: Undecided
So THIS is the culprit, an apache upload that matches the day when we began to
experience this:
* debian/apache2.2-common.apache2.init: Add stty sane so that users will get a
password prompt when using apache-ssl. (LP: #582963)
** Description changed:
Binary package hint: gdm
When
2010/9/8 Bilal Akhtar bilalakhta...@yahoo.com
From what I am seeing after grepping so much, I find out that its Apache
which resets the isig flag so that everything gets SIGQUIT on enter. Is
everyone over here having Apache2 installed?
--
Pressing enter at GDM screen crashes X
I have also apache installed.
** Patch added: stty sane commented
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/626723/+attachment/1556406/+files/apache2.init.patch
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug
RAOF: How can Upstart come in between? I don't think it registers
keypresses, does it?
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Has bug #554172 's workaround applied for Upstart got to do something
with this bug?
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
From what I am seeing after grepping so much, I find out that its Apache
which resets the isig flag so that everything gets SIGQUIT on enter. Is
everyone over here having Apache2 installed?
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug
VIOLA! EUREKA! Commenting out the call to stty sane in
/etc/init.d/apache2 worked like magic for me I know the problem now!
It doesn't affect Plymouth or X or GDM or Linux or Upstart, but Apache!
I am going to propose a patch.
** Also affects: apache2 (Ubuntu)
Importance: Undecided
So THIS is the culprit, an apache upload that matches the day when we began to
experience this:
* debian/apache2.2-common.apache2.init: Add stty sane so that users will get a
password prompt when using apache-ssl. (LP: #582963)
** Description changed:
Binary package hint: gdm
When
2010/9/8 Bilal Akhtar bilalakhta...@yahoo.com
From what I am seeing after grepping so much, I find out that its Apache
which resets the isig flag so that everything gets SIGQUIT on enter. Is
everyone over here having Apache2 installed?
--
Pressing enter at GDM screen crashes X
I have also apache installed.
** Patch added: stty sane commented
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/626723/+attachment/1556406/+files/apache2.init.patch
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug
Looking at what the other distros have been facing, I came to this
http://www.spinics.net/linux/lists/xorg/msg45959.html
Which init script is actually doing that?
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are
Same thing for me `Downgrading gdm to the version in lucid-updates does
not affect my ability to reproduce this bug`
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I still have the bug and I am willing to try a fix.
We can find the gdm lucid packet here :
http://packages.ubuntu.com/lucid/gdm
** Attachment added: The Xorg.conf output of the crashed
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/626723/+attachment/1552739/+files/Xorg.0.log.old
To install it : sudo sudo dpkg -i --force-downgrade
gdm_2.30.0-0ubuntu5_i386.deb
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Hmm I prefer to stay with aptitude, so this should work:
$ sudo aptitude install pkgname=version
and perhaps
$ sudo aptitude hold pkgname
So, now I need to know the package name and source, since I presume the
required package comes out of the lucid repos.
Currently,
$ aptitude versions gdm
i
In my bugfixes ppa, I have tried a hack to fix this bug. Its building
right now, I will test it before telling you people to use it, since it
could cause unexpected results right now.
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug
Nope, my PPA hack didn't work. This was using the same process that
fixed the problem in Lucid, that is, prevent plymouth from setting the
terminal to unbuffered input. Since the lucid fix had done most of it, I
disabled the remaining calls, but it didn't fix it. I suppose the
problem is different
@Chris Coulson: There's a related bug #625239 about X being started on
the wrong VT. You probably find that X crashes when you press enter
after about 5 minutes?
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a
Downgrading gdm to the version in lucid-updates does not affect my
ability to reproduce this bug, neither does downgrading Xorg to
1.8.99.905.
If plymouth hasn't changed in Maverick, is upstart a possible candidate?
That's in the plymouth/gdm/X transition path.
--
Pressing enter at GDM screen
I am moving over from bug #625239, which was actually a duplicate of
this one, but now that bug has been re-titled to reflect another
somewhat-similar bug. Triaging, since I think this is quite similar to
the one in the Lucid cycle, and enough information is available from
both the bugs for a dev
the issue started happening to quite some users again it seems but
neither plymouth nor gdm changes recently and it seems gdm is starting
on the right vt still, it probably needs debugging from somebody who
understand plymouth if that's not an xorg one
** Changed in: plymouth (Ubuntu Maverick)
I'm not sure if I'm seeing the same thing, but in my case X is starting
on tty2 alongside getty
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Mon, Sep 06, 2010 at 08:14:34AM -, Bilal Akhtar wrote:
I am moving over from bug #625239, which was actually a duplicate of
this one, but now that bug has been re-titled to reflect another
somewhat-similar bug. Triaging, since I think this is quite similar to
the one in the Lucid cycle,
Can you give me a pointer as to how to do that. I'm technical, so terse
instructions should do.
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug affect xsession started by kdm too. I'm using kubuntu maverick
beta.
--
Pressing enter at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can reproduce this locally.
Moving this bug to plymouth; it was the culprit in Lucid.
** Summary changed:
- gdm restarts on initial login
+ Pressing enter at GDM screen crashes X
** Description changed:
Binary package hint: gdm
When I boot an up to date maverick laptop, I am
27 matches
Mail list logo
