Well, steve, I know that because of this bug:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/506717
But, as you tell me, I will file a new bug-report.
--
plymouth killed SEGV signal
https://bugs.launchpad.net/bugs/550219
You received this bug notification because you are a member of Ubu
Frankly, karl, you have no way of knowing how many people this bug
affects because there's not enough information in this report to work
through it. The only user we can decisively say is affected by *this*
bug is the submitter, who no longer sees the bug. Please file a
separate bug report for an
not from my perspective. The problem does not affect only a few people,
anyway
--
plymouth killed SEGV signal
https://bugs.launchpad.net/bugs/550219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This was the only issue for me. The bug can be closed from my
perspective. Thanx for yoyr trouble!
--
plymouth killed SEGV signal
https://bugs.launchpad.net/bugs/550219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Steve,
I will do that next time. Apport is no longer reporting crashing at
boot, but I am getting other error messages prior to the grub screen
appearing. I will unsubscribe from this bug report and send a new one
with the error messages that are no appearing.
--
plymouth killed SEGV signal
http
same here. The SEGV message at every boot and the commands given by steve do
not work.
I have the prop. nvidia-driver running.
--
plymouth killed SEGV signal
https://bugs.launchpad.net/bugs/550219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The "could not connect to plymouth" message is bug #551062.
Is this now the only issue you're seeing? If so, I'll close this
report.
--
plymouth killed SEGV signal
https://bugs.launchpad.net/bugs/550219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
electhor,
You need to select "no, I need to file a new bug" when submitting the
apport crash report, otherwise none of your apport data is submitted to
a launchpad bug and you're just given the opportunity to comment on an
existing bug instead.
--
plymouth killed SEGV signal
https://bugs.launchp
The bug was reproducable across multible boots. Started this computer 15
minutes ago and so another message flashing after the boot. Something like "
mountall could not connect to plymouth#". Did the updates over the past 24
hours and rebooted. To my surprise worked plymouth again in low res.
Tn
Hmm...Did apport crash report - added to this post
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/543484 but the
crash report does not seem to have attached itself to the end of that
post. Let me know if you want it again or performed in a different
manner.
--
plymouth killed SEGV signal
There was no apport crash after I followed the commands that were sent
(and thank you for those), but upon a cold reboot, the same error
message appears prior to the grub screen loading. At reboot there is an
apport crash about plymouthd closing unexpectedly. I will send the
report.
--
plymouth k
Thank you for taking the time to report this issue and help to improve
Ubuntu.
Is this issue reproducible across multiple reboots? Is it reproducible
if you manually run plymouth after boot? To test: log out of X; press
Ctrl+Alt+F1 to switch to a console log in; log in; then run these
commands:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42269209/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42269210/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42269212/Dependencies.txt
** A
13 matches
Mail list logo
