** Changed in: plymouth
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (such as ci-info: messages)
To manage
so with this fix being added, we now see some annoying adaditional
output, I've filed bug 1303815 to track that.
** No longer affects: cloud-init (Ubuntu)
** Description changed:
During early boot, plymouth captures writes to /dev/console. As I
understand it, it is supposed to re-play tha
This bug was fixed in the package plymouth - 0.8.8-0ubuntu16
---
plymouth (0.8.8-0ubuntu16) trusty; urgency=medium
[ Steve Langasek ]
* Fix debian/patches/tty1-after-boot.patch: when we have multiple
non-default console options on the kernel commandline,
local_console_term
** Branch linked: lp:ubuntu/trusty-proposed/plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (such as ci-info: messages)
To manage notific
Hello Robie, or anyone else affected,
Accepted plymouth into trusty-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/plymouth/0.8.8-0ubuntu16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Branch linked: lp:ubuntu/plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (such as ci-info: messages)
To manage notifications about thi
Using a build from current lp:ubuntu/plymouth that has steve's fix for
bug 1160079 inside it, I no longer am losing data written to the
console!
I've tested this in a trusty kvm local image.
disk-patched.img had the new debs installed
disk-unpatched.img did not.
both images had https://bugs.freede
(oh yeah, above, the '103' was actually correct, as I modified the MAX
in that script to be 100).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (
plymouth-disabler has been accepted into the archive.
That could be used in the cloud images to reach the desired affect, but there
is some fallout.
I'd like to investigate some more actually getting the bug fixed in
plymouth and doing without plymouth-disabler. If that should occur, we
can remo
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/plymouth-disabler
/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (such as ci-
** Attachment added: "bootlogs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1235231/+attachment/3924816/+files/bootlogs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12352
On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold
boots), and compared the boot.logs.
My expectation is to have no less than 6 instances of each unique boot
messages, that is not the case:
1 * Starting Bridge socket events into upstart
1 * Starting modem con
Theres a plea for review/accept at
http://irclogs.ubuntu.com/2013/11/25/%23ubuntu-devel.html#t14:18 that is met
with 2 questions:
a.) why isn't this in plymouth package (because slangasek requested it not be)
b.) why isn't this in cloud-init package (because its not at all related to
cloud-ini
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=71996.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
filed upstream under bug
https://bugs.freedesktop.org/show_bug.cgi?id=71996 .
** Bug watch added: freedesktop.org Bugzilla #71996
https://bugs.freedesktop.org/show_bug.cgi?id=71996
** Also affects: plymouth via
https://bugs.freedesktop.org/show_bug.cgi?id=71996
Importance: Unknown
irc conversation response to comment 21.
11/21/13 14:24:54 so would you NAK a proposal to put
'plymouth-disabler' into 'plymouth' packaging ?
11/21/13 14:25:15 i'd like to get that in quick and be done with it.
and it really has nothing to do with cloud-init, but everythign to do with
plymout
Steve,
Why would you suggest cloud-init as a [source] package for this?
The fact that plymouth is broken is completely unrelated to cloud-init or
ubuntu use as a guest at all.
Wouldn't it be better to put this package closer to plymouth, so it is
more likely to be updated if ever needed?
-
Steve,
Do you think this can be fixed in plymouth correctly?
If not, and you still would recommend .override files which of the
following solutions would you think is best (or another you suggest):
A.) 'disabler' package built by 'plymouth' source package (sugg name:
plymouth-disabler)
B.) 'dis
I think the cloud-init *binary package* should add these .override files
as conffiles. While the issue of messages going missing may affect
systems other than cloud images, it's precisely the cloud images where
a) plymouth adds no value, and b) the impact of messages going missing
from the console
** Description changed:
During early boot, plymouth captures writes to /dev/console. As I
understand it, it is supposed to re-play that content later. Whether or
not it intends to is not the issue. In our cloud-images (and in other
cases) users may write data to /dev/console that needs
20 matches
Mail list logo
