Ventura 13.0
DisplayLink 1.7.0 (build 60.120)
I'm having the issue where in the morning after waking my Macbook Pro M1 from sleep, my display using DisplayLink doesn't turn on. I've observed sometimes DisplayLink Manager doesn't launch on cold boot, but I have added it to "Login Items" both "DisplayLink Corp" and "DisplayLink Manager" are allowed.
But going back to resuming from a sleep, the DisplayLink Manager is still running in the top menu bar. It seems I have to troubleshoot the monitor if its not recognized. Sometimes I have to restart DisplayLink Manager, sometimes DisplayLink Manager randomly closes (not closed by choice, it must be crashing)
Editing my post:
3 hours after I made this post, it looks like the monitor experience issues went blank again. Troubleshooting this issue, I realized I forgot to mention I'm using a StarTech USB 3.0 to Dual DisplayPort Adapter 4k 60hz Adapter. When I started troubleshooting the issue, I observed DisplayLink Manager couldn't recognize a display. I restarted the app a few times with no luck. I unplugged the adapter and reseated it with no luck. I unplugged the adapter and connected the DisplayPort cable directly into a DisplayPort port on my CalDigit thunderbolt port and the display worked. I then took the USB3 to DisplayPort adapter and plugged it into my Windows 10 PC, after a few moments, the drivers installed and initialized, and the display worked.
Once I took the USB3 Adapter out of my PC and plugged it back into my CalDigit Dock, the DisplayLink Manager software still wasn't able to recognize the display. I then started to believe the CalDigit Thunderbolt Dock was faulty? Once I opened up a new Safari tab to search for common CalDigit issues, I realized my internet wasn't functioning. Cable modem was fine, ethernet port was blinking on the Router and CalDigit Dock... I unplugged the thunderbolt cable from Mac to Dock and reseated it and boom all displays immediately displayed output.
Still not sure what's going on, perhaps the cable is going bad? USB-C port going bad? CalDigit going bad? If this issue continues, I'll update this thread.