ubuntu-x-swat team mailing list archive

[Samuel thibault <samuel.thibault@xxxxxxxxxxxx>]

Bryce Harrington, le Thu 08 Oct 2009 00:39:09 -0000, a écrit :
> On Wed, Oct 07, 2009 at 11:46:20PM -0000, Samuel thibault wrote:
> > Bryce Harrington, le Wed 07 Oct 2009 23:31:46 -0000, a ??crit :
> > > On Wed, Oct 07, 2009 at 10:44:02PM -0000, Samuel thibault wrote:
> > > > Bryce Harrington, le Wed 07 Oct 2009 22:30:13 -0000, a ??crit :
> > > > > On Wed, Oct 07, 2009 at 10:13:20PM -0000, Samuel thibault wrote:
> > > > > Hi Samuel, would mind proposing a patch?  I'm a bit of a novice with
> > > > > upstart scripting, and fairly distracted by mesa at the moment.
> > > > 
> > > > It should just be a matter of adding keymaps.sh and console-setup to the
> > > > Should-Start field of the /etc/init.d/gdm,kdm,xdm scripts
> > > 
> > > That sounds like it's getting a bit out of the scope of this bug
> > > report.
> > 
> > ? It's precisely in scope: as I said, Xorg gets EIO because the tty gets
> > a hung up after Xorg is started, most probably because the console
> > initialization scripts may get started after Xorg is started.
> 
> No, patching gdm and kdm is well outside the scope of xorg-server, which
> is what this bug is filed against.  If you believe this to be the only
> way to solve it, the bug should be refiled against those packages.

Yes I do, see my comments: I believe Xorg just gets started too early,
before the console is setup, and that's gdm/xdm/kdm's responsibility.

-- 
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.