|
06-06-2019, 09:29 AM | #1 | |
Junior Member
Join Date: May 2019
Posts: 9
|
Quote:
What I've found is that this always happend earlier in the day and it was happening when the network was very busy (backups being uploaded to the NAS). Since I've switched to plugging in the network cable directly into my machine that has resolved this issue for me. I don't particularly use the USB ports on my device, but I suspect heavy USB port usage could also have a similar impact. Last edited by rick_pri; 06-06-2019 at 09:30 AM. Reason: Slight addition for clarity |
|
06-06-2019, 12:50 PM | #2 | |
Junior Member
Join Date: Nov 2018
Posts: 8
|
Quote:
|
|
06-17-2019, 08:39 AM | #3 | |
Junior Member
Join Date: May 2019
Posts: 9
|
Quote:
Code:
Alt+F2 If that does nothing can you Code:
Ctrl+F2 Code:
sudo service displaylink-driver restart I've found that sometimes the display manager would have issues with not displaying onto my internal screen (it would still act as if the display was disabled - as I used to have my laptop lid closed whilst using the other monitors.) There may be something in the Code:
/var/log/syslog |
|
07-23-2019, 02:45 PM | #4 |
Junior Member
Join Date: May 2019
Posts: 9
|
Thumbs up for the latest release from me
I can confirm that my issue on startup where it looked like my machine was frozen has gone with the latest release and has been fine since release day (now my machine boots just as I would expect it to, without the ~5min delay in startup and the requirement to do the CTRL+F2, CTRL+F1 dance to get the GDM screen to appear.)
Let's hope that it continues to work with the 19.10 release later this year (I tend to do day 1 updates, and sometimes I jump onto the beta/RC releases if I have a particularly annoying issue which is fixed in the newer version.) |
Tags |
ubuntu 19.04 |
|
|