Seems to me, that ubuntu did not configure all packages after an
atualization, and when I do a reboot, I get a plymouth error. I've tried
to enter in recovery mode, of an older kernel and log to root password.
So, in terminal, after type these commands bellow, the system started
normally again. I h
If you are not Ralf Hildebrandt, do not reopen this bug report. Please
file a new bug report instead for your issue.
** Changed in: plymouth (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
In fact, adding a "dev /dev" line (as suggested in comment 48) to fstab
is a disaster: it over-mounts a good /dev directory with an empty one,
and then boot really screws up, since there are not /dev/tty's any more,
and so getty fails ... ugh.
--
You received this bug notification because you are
this bug was marked "invalid", I just changed it back to "new". Don't
see what's invalid about it -- many people have been bit by this, its
been many years, and the very latest, greatest, fresh-out-of-the-box
Ubuntu release still has this bug. Booting ubuntu has become a
nightmare the last few ye
The "add a dev /dev line to fstab" solution does not fix the problem.
** Changed in: plymouth (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571258
Title:
plym
still crashing after update from oneiric to precise pangolin. Bummer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571258
Title:
plymouth main process (341) killed by SEGV signal
To manage notifi
It doesn't make any sense that you should have to manually add /dev to
/etc/fstab; this mount point is already listed in /lib/init/fstab, which
is shipped in the mountall package and is processed before udev is
started. It sounds like there is some deeper problem with your system
configuration dive
I had same issue trying to boot with custom kernel (3.1.6) on Ubuntu 11.04
Booting froze and after editing grub for non-silent, I could see the following:
init: plymouth main process (940) killed by SEGV signal
init: plymouth-splash main process (940) terminated with status 2
Though the final log
@Melroy:
Yes, that's what I meant. Here it works like a charm, although not on ARM but
x84 and x86_64 (see ftp://ftp.ovh.net/made-in-ovh/bzImage/ for complete configs)
Also, try if you don't have a login mask on another tty (ctrl+alt+F2 for
example), since it may happen that dying plymouth proces
@Felix:
Do have:
CONFIG_SYSFS=y
I can try to set:
CONFIG_DEVTMPFS_MOUNT=n
Like it was before...
But:
# CONFIG_SYSFS_DEPRECATED_V2 is not set
(=n is the same as is not set I guess?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Melroy: what about CONFIG_SYSFS_DEPRECATED*? (should be =n in my
experience.)
Also I tend to set CONFIG_DEVTMPFS_MOUNT=n
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571258
Title:
plymouth main p
Same problem. Using my custom ARM kernel to boot Ubuntu. I tried to set
CONFIG_CONNECTOR & CONFIG_INOTIFY. I set CONFIG_TMPFS, CONFIG_DEVTMPFS
and CONFIG_DEVTMPFS_MOUNT I tried to disable unreadahead (by renaming
/etc/init/unreadahead .conf to unreadahead.disable) because I use an SD-
card. Finally
I hit this too, and so far, its been stunningly painful to work around.
I have to run a custom kernel because I run RAID, and the stock Ubunutu
kernels+initrd have never been able to handle having the root volume on
RAID.
The older Ubuntu installs (e.g. dapper, feisty, jaunty) had installers
that
Either plymouth or plymouth-splash, I just found this issue existing in
my system was caused by /etc/fstab file corrupt, then it won't mount all
file systems, so please have a check on syslog if possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Tom,
The Ubuntu experience includes an Ubuntu kernel with which your issue is
not reproducible. If you choose to use an upstream kernel with an
arbitrarily different configuration, it's incumbent on you to tell *us*
what the relevant config difference is that triggers this, if you think
this is a
Is this the Ubuntu experience?
Because of this bug, the issue that it is impossible to have a
cryptsetup passphrase prompt at boot for non-Ubuntu-packaged kernels
(i.e. using the kernel.org sources and make-kpkg) is still unresolved.
Similar bugs have been reported more than a year ago!
e.g.
htt
FWIW, I also see the plymouth main process "SEGV" when starting a 10.10
AMI image under KVM 10.04, with 'console=ttyS0' on the kernel command
line. This is similar to the OP's report, except that I see plymouth-
splash terminate first, and then plymouth main SEGV.
...
[1.480006] EXT4-fs (vda):
Same here, however, this occurred first after the file system had to be
checked due to the necessary number of prior boots. From then on it
freezes. Now I can boot if I unplug the power chord of my notebook
(X61t) and thereby skip the fs check
--
plymouth main process (341) killed by SEGV sig
> init: plymouth-splash main process (586) terminated with status 1
That is not the same bug at all. Please file a separate bug report for
your issue.
Setting this bug back to incomplete as we're still waiting from input
from the bug submitter.
** Changed in: plymouth (Ubuntu)
Status: Co
I'm pretty sure I'm having this issue too. I cannot boot into Ubuntu at
all, as the boot crashes both in normal and recovery mode. I tried
recovery mode and wrote down everything that appeared on the screen. It
was:
udev[349]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}=
I have the same issue. Boot frequently hangs with blinking cursor top
left. Can only power down and retry. Happens about 50% of the time. Rest
of the time get "plymouth main process terminated" etc. as described in
previous posting.
--
plymouth main process (341) killed by SEGV signal
https://bug
Architecture: i386
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: LENOVO 43192PU
NonfreeKernelModules: nvidia
Package: plymouth 0.8.2-2ubuntu2
PackageArchitect
I've just installed fresh ubuntu 10.0.4. The problem is that system boots
completely 1 out of 3 attempts.
After I select ubuntu in grub menu I get a blank screen with blinking cursor.
Then after some time (30-60 seconds) I either get "plymouth main process (xxx)
killed by SEGV signal" and boot p
Appendix:
When booting the current distribution kernel, linux-
image-2.6.32-24-generic, booting works without the crash/SEGV.
When booting the current stable 2.6. kernel from kernel.org (2.6.34.1),
the boot stalls at the password prompt with the abovementioned SEGV and
error messages. When enteri
I use dm-crypt/LUKS and therefore need the passphrase prompt.
After upgrading to Lucid, I am affected, too. Instead of the passphrase prompt,
there are the same error messages than the original author of this bug report
has:
> plymouth main process (xxx) killed by SEGV signal
> plymouth-splash m
** Also affects: plymouth
Importance: Undecided
Status: New
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Solve this problem by enable the "kernel mode setting" options in the
kernel config.
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
still waiting for feedback from the original submitter, per comment #12.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ub
same problem here; I also use a custom kernel; after rebooting with
lucid the plymouth SEGV messages were the last thing I could see. had to
reboot with init=/bin/bash and notice that upstart must have failed to
fsck and remount,rw my rootfs
--
plymouth main process (341) killed by SEGV signal
ht
Fixed my actual issue that was masked by these plymouth errors - a basic
error in network/interfaces.
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/512253
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification beca
Same problem here. For me it helps to remove "quite splash" from the boot
options.
I tried a stock and a custom kernel both fail to boot with quite and quite
splash.
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification be
I fixed my networking issue. here is the link
http://ubuntuforums.org/showthread.php?p=925#post925
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I see the plymouth error in recovery mode. In normal mode, I'm able to
boot without network connectivity, how can fix this connectivity
problem.
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member
Please update the status if fixed.
Thanks.
Rajeev
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
* Steve Langasek :
> Ralf,
>
> Is it reproducible if you boot without the 'quiet splash' boot
> arguments?
Yes.
> If so, can you boot without 'quiet splash' and with '--verbose' added to
> the boot options and report the last output when booting this way?
I can try that once I'm back from vaca
Ralf,
Is it reproducible if you boot without the 'quiet splash' boot
arguments?
If so, can you boot without 'quiet splash' and with '--verbose' added to
the boot options and report the last output when booting this way?
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad
* Steve Langasek :
> Ralf, are you also using a non-Ubuntu kernel when you boot?
No.
> I don't know what kernel options are required in order to use plymouth.
> However, plymouth crashing should only stall the boot if interaction is
> needed - such as because an fsck failed or a passphrase is ne
Ralf, are you also using a non-Ubuntu kernel when you boot?
I don't know what kernel options are required in order to use plymouth.
However, plymouth crashing should only stall the boot if interaction is
needed - such as because an fsck failed or a passphrase is needed to
decrypt a disk. So I don
After purging ureadahead and adding CONFIG_DEVTMPFS=y as well as
CONFIG_DEVTMPFS_MOUNT=y in my kernel, I can now boot beneath that point
where plymouth crashed before.
It would be nice to document that dependency somewhere.
Now my systems still don't boot completely, but it seems that's rather
du
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Correction: I still get (part of) the message, it was simply hidden by debug
output.
Interestingly the server now pings (static network configuration, no
NetworkManager). Services aren't started at all, Logs are not written to disk.
New screenshot attached.
** Attachment added: "plymouth2.png"
# apt-cache show ureadahead
[...]
ureadahead requires a kernel patch included in the Ubuntu kernel.
[...]
# aptitude purge ubuntu-minimal ureadahead
# reboot
I don't have that message anymore (but the system still doesn't boot up
completely)
--
plymouth main process (341) killed by SEGV signal
Same here: Any solution?
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
Same here: When booting on a kernel that is optimised for headless usage
on dedicated servers, plymouth quits ungracefully. I tried adding "--
debug" in /etc/init/plymouth.conf, which leads to the following output:
(see screenshot)
System: Ubuntu Server 10.04 (both 32 and 64bit)
Kernel: vanilla 2.
This bug is affecting me too, but it happens only when (and everytime) I boot
my machine with my own custom kernel (compiled from ubuntu kernel source
package using kernel-package).
When i boot the stock kernel that I'm keeping "just in case" (at present
2.6.32-21) everything works fine.
Syste
The machine had been rebooted using a grml rescue disk and after that I
used ubuntu-bug to report this...
--
plymouth main process (341) killed by SEGV signal
https://bugs.launchpad.net/bugs/571258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "plymouth.png"
http://launchpadlibrarian.net/45975459/plymouth.png
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/45975142/BootDmesg.gz
** Attachment added: "CurrentDmesg.gz"
http://launchpadlibrarian.net/45975143/CurrentDmesg.gz
** Attachment ad
47 matches
Mail list logo
