Serious enough on my 2 systems to fatally lock up one system repeatedly. Two machines both running 16.04 lts. One locks up frequently with this error. The other only ocassionally. Both 64 bit AMD running on SS drives.
Humbly request a pointer to a printable version of the error report contents. Now taking 4 screenshots to capture the details. What else should I preserve that might assist in the resolution of this bug? I seem to also suffer from related but different bugs, most showing up in Plymouth. I corrected a few bits of corrupted code in the past which seemed to eliminate this class of bug for a few weeks. All drives report healthy (ext4) Most commonly occur right after sign on and the opening of G3 desktop. Suggests possible radiation damage with SSDs Usually I tell the system to ignore the error and it does not return that powered up session. Do I need to purchase better SSDs with more robust error correction? Have one Samsung, one kingston. At 2500 feet so a bit more radiation than sea level. Humbly request forebearance in the face of my ignorance. Most of my software skills were obsolete decades back. I no longer have enough remaining life or intellectual power to come anywhere close to the ability to understand this code. I would if I could. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542000 Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1542000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
