Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"

To: Scott Barker <scott@mostlylinux.ca>, 570382@bugs.debian.org
Subject: Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
From: dann frazier <dannf@debian.org>
Date: Fri, 27 Aug 2010 16:02:55 -0600
Message-id: <20100827220255.GD23408@lackof.org>
Reply-to: dann frazier <dannf@debian.org>, 570382@bugs.debian.org
In-reply-to: <20100827181300.GD1972@mostlylinux.ca>
References: <alpine.DEB.2.00.1008232142430.6246@tpo-laptop> <878w3vtkhf.fsf@algae.riseup.net> <20100827181300.GD1972@mostlylinux.ca>

On Fri, Aug 27, 2010 at 12:13:00PM -0600, Scott Barker wrote:
> After applying the latest kernel package, all of my VMs started just fine as
> well. All i386.

Well, this is good news I suppose.. personally I'd rather have
something 100% reproducing than intermittently failing :(

-- 
dann frazier

Reply to:

References:
- Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
  - From: Tomas Pospisek <tpo@sourcepole.ch>
- Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
  - From: micah anderson <micah@debian.org>
- Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
  - From: Scott Barker <scott@mostlylinux.ca>

Prev by Date: Re: Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
Next by Date: Re: Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
Previous by thread: Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
Next by thread: Bug#591951: linux-2.6: should suggest extlinux as an alternate bootloader on x86
Index(es):
- Date
- Thread