![fs 16 crashes mobile fs 16 crashes mobile](https://i.ytimg.com/vi/t_9gJ9aG0ew/hqdefault.jpg)
I don't do a lot of tinkering with system settings, and hadn't messed with anything in a while when the first crash happened. I can be doing anything in any of those (or other applications) when this happens. I spend most of my time in Chrome, Pycharm, and the command line. As far as I can tell, nothing I'm doing triggers this response.But here are a few other thoughts that might be useful: Other than that, I don't have other concrete data points to help nail down what's going on. systemd-journald: Failed to write entry ( items bytes), ignoring: Read-only file system.EXT4-fs error (device nvme0n1p2) ext3_find_entry:1436: inode#: comm gmain: reading directory lblock 0.The error messages from this last crash, which are repeated continuously until I hard shutdown are:
![fs 16 crashes mobile fs 16 crashes mobile](https://www.mdpi.com/ijerph/ijerph-16-03565/article_deploy/html/images/ijerph-16-03565-g004.png)
The behavior is very similar to the 16.04 crashes, though the error messages and speed of the crash seem somewhat different. In the week since the upgrade, 18.04 has crashed twice. I did not do a clean install, but upgraded instead. So I decided to try upgrading to Ubuntu 18.04 to see if that would solve the issue. I ran Lenovo's builtin hardware diagnostics, and everything comes back fine.
#Fs 16 crashes mobile windows
Application windows stop responding or rendering.For the next two weeks after that, it was completely stable and didn't freeze once. Over the next couple of weeks, it did this a half dozen times. I restarted it, and it went back to normal for a week or so before doing it again. A couple of months ago, I had been using Ubuntu 16.04 on a Thinkpad T570 for a year or so, when my laptop windowing crashed for the first time.