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 plymouth bug that we should fix.
Regardless, this is a bug report by Ralf Hildebrandt, who reported a
segfault when using the stock Ubuntu kernel package, not a custom
kernel. So your issue is unlikely to be related to his. Please file a
separate bug report for your issue and, as I said, please tell us what
*specific* kernel configuration differences trigger this issue.
Due to the lack of feedback from Ralf, I'm closing this bug report as
invalid to avoid further conflation of unrelated bugs. We can reopen
this report if further information about Ralf's issue becomes available.
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Invalid
** Changed in: plymouth
Status: New => Invalid
--
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
