1) roger@roger-desktop:~$ sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 [sudo] password for roger: Reading package lists... Done Building dependency tree Reading state information... Done linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62). xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1). The following packages were automatically installed and are no longer required: libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab python3-reportlab-accel python3-sip Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. roger@roger-desktop:~$ Or do you mean results as to boot with no problems? - No change to that on earlier experience, but now after additional other updates, and using Xdiagnose with various settings, I haven't seen a boot problem for a few updates. I will continue to monitor for a few days with Xdiagnose off to assure that problem is really gone. In retrospect, it appears likely to me that there was a borderline timing problem in the boot sequence, and something in the meantime (almost daily updates, or ???) may have changed that, or maybe I've just been lucky the past 8 or 10 tries. Continued watching is appropriate. Also, the command " sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 " actually causes a problem in my system. It sets and locks the theme to Ambiance, even though the setting properly shows Adwaita. It will not allow the theme to be reset until I reboot into Unity desktop which then allows it to reset properly to Adwaita. I don't know if this is a bug, or just the way it works for diagnostic purposes. If it's just the way it works, it should be described in the documentation along with the fix. If it's a bug, I'll leave it to others for now. 2) roger@roger-desktop:~$ ls -la /var/crash total 8 drwxrwsrwt 2 root whoopsie 4096 May 29 03:46 . drwxr-xr-x 15 root root 4096 Dec 17 2016 .. roger@roger-desktop:~$ 3) "To confirm, is there a reason you are using the non-default kernel parameters (i.e. WORKAROUND a problem): plymouth:debug drm.debug=0xe nopat vesafb.invalid=1" - I'm not familiar with that line. I can guess two possibilities: - - Something very old in the system, perhaps done to deal with an earlier difficulty - - Some connection with Xdiagnose, which I have been experimenting with previously in connection with this problem (now all settings inactivated as of today). 4) "If you remove the non-default kernel parameters does this influence the reported issue: plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 " Please tell me before I deal with this if this is possibly something done by Xdiagnose, and how to best remove it if that seems advisable. Thanks! -----Original Message----- From: Christopher M. Penalver