The difference between them, as far as I can tell, that that bug (1657907) logs a firmware crash, and this one (1668031) does not. I cannot, however, actively provocate the one or the other.
Are you able to see, if this bug is actually a different one?
My current workaround is, that I constantly have 2 terminal emulator windows open: one that is pinging google, so that I can see, when the connection is gone, and one in which I `sudo service network-manager restart`, when it is.
Hello Joseph,
That's not so easy to confirm (for upstream).
In the cause of confirming this bug - https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1657907 - I've installed an upstream kernel and that bug was still present, and it also occurs every hour or so.
The difference between them, as far as I can tell, that that bug (1657907) logs a firmware crash, and this one (1668031) does not. I cannot, however, actively provocate the one or the other.
Are you able to see, if this bug is actually a different one?
My current workaround is, that I constantly have 2 terminal emulator windows open: one that is pinging google, so that I can see, when the connection is gone, and one in which I `sudo service network-manager restart`, when it is.
Let me know, if there is anything else I can do.