[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

2018-08-30 Thread Joe Marty
I spoke too soon. I'm now getting the same error in the new VM, which was created from scratch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1433320 Title:

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

2018-08-28 Thread Joe Marty
Incidentally, I only get this bug in a virtual machine that I had "copied" from one computer to another. I was able to re-create the virtual machine from scratch (using the same install image, and installing the same software, etc) on the new computer, and did not get the same issue in the new

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

2018-08-20 Thread Joe Marty
I don't know if this will help, but here's the vmware log: ** Attachment added: "VMWare log after crash and restart" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/+attachment/5178236/+files/vmware.log -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

2018-08-20 Thread Joe Marty
I'm having this same error occur on a new Ubuntu 18.04 VM, on VMWare Player. I don't understand why it was marked as "won't fix" for systemd... ? This is happening when I suspend my host machine (windows 10). Upon resuming, the VM has crashed and goes through the startup process, then reports