Didn't work for me on Bionic. However since this mornings massive update (Bionic) didn't get it on subsequent reboot. So, keeping fingers crossed ...
On Fri, Mar 23, 2018 at 10:35 AM Milan Jovanovic <milanm...@gmail.com> wrote: > I can confirm that after doing dpkg-reconfigure plymouth the issue is > not appearing (no errors showing) > > ---- > > $ apt-cache policy plymouth > plymouth: > Installed: 0.9.3-1ubuntu2 > Candidate: 0.9.3-1ubuntu2 > Version table: > *** 0.9.3-1ubuntu2 500 > 500 http://rs.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > ---- > > $ lsb_release -rd > Description: Ubuntu Bionic Beaver (development branch) > Release: 18.04 > > ---- > > 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018 > > ---- > > Still, not sure if related to this, the cursor still dissapearing on the > login screen. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/927636 > > Title: > plymouthd crashed with SIGSEGV in script_obj_deref_direct() > > Status in Plymouth: > Confirmed > Status in plymouth package in Ubuntu: > Triaged > > Bug description: > Ubuntu 12.04 LTS (development branch) > > ProblemType: Crash > DistroRelease: Ubuntu 12.04 > Package: plymouth 0.8.2-2ubuntu28 > ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 > Uname: Linux 3.2.0-14-generic x86_64 > NonfreeKernelModules: fglrx > ApportVersion: 1.91-0ubuntu1 > Architecture: amd64 > Date: Mon Feb 6 07:03:15 2012 > DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth > ExecutablePath: /sbin/plymouthd > MachineType: Foxconn AMD HDZS01 > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic > root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7 > ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session > ProcEnviron: PATH=(custom, no user) > ProcFB: 0 VESA VGA > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic > root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7 > SegvAnalysis: > Segfault happened at: 0x7effe6b50ea0 <script_obj_deref_direct>: > cmpl $0x1,(%rdi) > PC (0x7effe6b50ea0) ok > source "$0x1" ok > destination "(%rdi)" (0x00000000) not located in a known VMA region > (needed writable region)! > SegvReason: writing NULL VMA > Signal: 11 > SourcePackage: plymouth > StacktraceTop: > script_obj_deref_direct () from /lib/plymouth/script.so > script_obj_as_custom () from /lib/plymouth/script.so > script_execute_object () from /lib/plymouth/script.so > script_lib_plymouth_on_update_status () from /lib/plymouth/script.so > ?? () > TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth > Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > dmi.bios.date: 04/19/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: A93F1022 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: AHD1S > dmi.board.vendor: Foxconn > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrA93F1022:bd04/19/2011:svnFoxconn:pnAMDHDZS01:pvrTobefilledbyO.E.M.:rvnFoxconn:rnAHD1S:rvr: > dmi.product.name: AMD HDZS01 > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Foxconn > > To manage notifications about this bug go to: > https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions > -- This email is printed from 100% recycled electrons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927636 Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct() To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
