Posting this as an informative notification:
It seems this fix probably causes regression bug #1105807.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling
This bug was fixed in the package upstart - 1.5-0ubuntu7.2
---
upstart (1.5-0ubuntu7.2) precise-proposed; urgency=low
* Cherry-pick newer test code to fix test failure seen
on ARM (LP: #980917).
-- James Hunt james.h...@ubuntu.com Thu, 17 Jan 2013 11:39:27 +
** Changed
The 1.5-0ubuntu7.2 fix the bug here (Ubuntu Core 12.04 on armhf).
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Hello Tim, or anyone else affected,
Accepted upstart into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/upstart/1.5-0ubuntu7.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Branch lp:~jamesodhunt/ubuntu/precise/upstart/sru-bug-980917 updated and
new package created and uploaded (upstart_1.5-0ubuntu7.2) to correct
build failure seen on ARM.
Note that the changes are purely test code changes: the code for Upstart
itself has not changed in this new version.
--
You
The fix released here fixed my issue, upstart version: 1.5-0ubuntu7.1
$ dpkg -s upstart
Package: upstart
Status: install ok installed
Multi-Arch: foreign
Priority: required
Section: admin
Installed-Size: 1172
Maintainer: James Hunt james.h...@ubuntu.com
Architecture: i386
Version: 1.5-0ubuntu7.1
Hello Tim, or anyone else affected,
Accepted upstart into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/upstart/1.5-0ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:~jamesodhunt/ubuntu/precise/upstart/sru-bug-980917
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job [SRU]
To manage
** Patch added: source package diff for Upstart 1.5-0ubuntu7 in Precise
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+attachment/3440350/+files/ubuntu-precise-upstart-1.5-0ubuntu7.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: source package diff for Upstart 1.5-0ubuntu7.1 in Precise
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+attachment/3440351/+files/ubuntu-precise-upstart-1.5-0ubuntu7.1.diff
** Changed in: upstart (Ubuntu Precise)
Status: In Progress = Fix Committed
--
There is currently no formal SRU branch for Precise, hence the debdiffs
above. These changes are also in branch:
lp:~jamesodhunt/ubuntu/precise/upstart/sru-bug-980917
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstart version 1.5-0ubuntu7.1 has been uploaded to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job [SRU]
To manage
what needs to happen to have this backported into precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job [SRU]
To manage
I should note that I've manually installed the quantal 1.5-0ubuntu8
upstart package in my precise VM and the 'failed to create pty' errors
are gone, and everything else of mine is working fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Will this fix be ported in 12.04.1 or it has already escaped test plan
for .1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job [SRU]
To
This bug was fixed in the package upstart - 1.5-0ubuntu8
Thanks a lot! Works like a charm now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging
This bug was fixed in the package upstart - 1.5-0ubuntu8
---
upstart (1.5-0ubuntu8) quantal; urgency=low
* Merge of latest upstream including doc fixes, fixes for booting
on initramfs-less systems and improved error handling in spawn
failure scenarios (LP: #980917,
** Description changed:
+ [PROBLEM]
+
+ This bug causes Upstart to display 1 error message / job that is started
+ that should have its output logged (by default ''all'' jobs are thus
+ affected) if it is unable to create a pseudoterminal device, which is
+ required for Upstart job logging.
+
+
good! anyway better than a crowd decided to change init etc with _no_
knowledge at all
On Thu, Jul 26, 2012 at 8:24 PM, Steve Langasek
steve.langa...@canonical.com wrote:
James has taken a crack at this and found it to appear not to be
unintrusive, or at least not tractable in time for .1.
James has taken a crack at this and found it to appear not to be
unintrusive, or at least not tractable in time for .1. Postponing to
.2.
** Changed in: upstart (Ubuntu Precise)
Milestone: ubuntu-12.04.1 = ubuntu-12.04.2
--
You received this bug notification because you are a member of
I got this message in vnc when I ran virtual machine of ubuntu 12.04 with the
default kernel 2.6.32-41-server then with the updated kernel 3.2.0-24-generic
but error still persist.
I can login to the vm may be because --no-logs option in the /boot/grub.cfg.
output of the kernel ring buffer
[
The most important system processes run without logging, and you can't justify
a higher priority?
This issue looks _critical_ to me, all the more so as the users are already
having obscure problems they're unable to trace.
Hope you solve it soon and wish you good luck!
--
You received this
So, running without an initramfs isn't currently a supported
configuration due mainly to bugs such as this, although we would like to
make it so in future for various reasons. As such I can't currently
justify a priority higher than Medium. However, if the fix turns out
not to be too intrusive
James,
Is it conceivable that we will see a fix released in time for the
Ubuntu 12.04.1 release in August? I think it's taken quite a bit longer
than need to triage this bug and determine the priority of the fix.
It's affecting quite a large number of people on different platforms.
I'm simply
Hi,
I am working on a Pandaboard ES.
I try to boot my Pandaboard over NFS, using Ubuntu 12.04
My NFS connection is OK, but it stops during the start of modules.
When I boot the same fs, using an SD card, it works fine.
(I use the kernel option --no-log in order to avoid init: Failed to create pty
James Hunt (jamesodhunt) wrote on 2012-04-25: #5
@Adam: the point here is that Upstart is signalling an error, albeit a
soft one. However, in all cases it will be a transitory error since at
some point in the boot /dev/pts _will_ be mounted.
Aparently that isn't the case. I'm booting with
Christopher: Would you be able to clarify how your upgrade going
sideways is related to a bug in Upstart when /dev/pts isn't mounted by
an initrd?
-Tim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In my case, a seemingly plain-vanilla, straightforward upgrade from
Ubuntu 10.04 LTS on Ubuntu-supported hardware (leo1 from System76) to
Ubuntu 12.04 resulted in an inability to boot into anything more than
GRUB, and also (once the system was booted) no DNS.
I detail my successful fix, and the
I have exactly the same error on a brandnew precise-upgrade on an i386
system (Toshiba SM-30 Laptop).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling
The behaviour seems wrong to me - I believe it needs to be changed so
that it follows the previous expected (and acceptable) model. As a bit
of a metaphor, if Toyota released a new car but all the new cars had a
red warning light on them and Toyota's fix was You all have to press a
button in the
Thanks for the feedback on having a more concise error message perhaps
this is something that could be improved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty -
@Adam: the point here is that Upstart is signalling an error, albeit a
soft one. However, in all cases it will be a transitory error since at
some point in the boot /dev/pts _will_ be mounted.
For i386/amd64 Ubuntu images, Ubuntu currently uses an initramfs which
is responsible for setting up
James: It seems that this is a chicken and egg problem when someone
doesn't have an initramfs. I'm quite alright with logging being
disabled if /dev/pts isn't mounted. The problem I have is the large
amount of unhelpful errors that are printed on the console. If this
could be a concise error,
I'm having this same bug on the ARM port of Ubuntu. I have
LEGACY_PTYS=y, LEGACY_PTY_COUNT=256, and UNIX98_PTYS=y on my custom
2.6.35 kernel (this is for the HP TouchPad tablet computer btw) and
after the system is booted there are /dev/ptmx, /dev/pts, and /dev/ptyXX
entries in the system. I get
Hi Tim - the messages you are receiving are expected behaviour since
Upstart is signalling an error condition - the environment it expects is
not correct. Upstart currently expects /dev/pts to be mounted and the
/dev/ptmx device to exist by the time it starts. On Ubuntu, this is
currently handled
Hello James,
Thank you for taking the time to look in to this bug as well as get back
to me. The explanation of the issue definitely makes the problem more
clear. However, I am intrigued by the fact that something so important
is assumed, and that Upstart errors when it encounters something
** Tags added: precise ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
** Description changed:
I believe this bug is in Upstart due to similar bug that was recently
fixed:
- https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667
I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the
previous bug was fixed, I still received the
39 matches
Mail list logo
