Framework 13 display on but not "active" from start with docking station

Overview

I am running a Framework 13 (AMD Ryzen 7 7840U) and using a Dell D6000 docking station with 2 external displays. All 3 screens laptop and both external monitors are usually in use. I am running Fedora 43 KDE.

Background

I am aware that the DisplayLink driver is a bit of a pain with the Dell D6000. I used the following github to download the latest RPM at the time I installed - LINK

I just looked and I am using - fedora-43-displaylink-1.14.12-1.github_evdi.x86_64.rpm and it looks like there is a 1.14.14-1 available. I will upgrade to this shortly.

The Issue

When powering on the laptop when it is connected to the docking station the framework display comes on and looks like it is working but I am not able to move my mouse cursor to the laptop display or use it in any way. The 2 external displays work just fine.

Attempted fixes and testing

If I unplug the USBC cable to the dock all open applications move to the laptop display and work fine. I then can plug in the USBC and then all 3 displays work fine again.

If I power up the system, notice the laptop display is not working, and reboot i believe all 3 displays work. I need to test this again.

I am going to attempt the reboot testing as well as upgrading the displaylink rpm package as next steps.

Thank you for any and all help :slight_smile:

Power-up test

Before attempting a reboot test I did 2 power-off and on tests and the laptop display seemed to work fine with these power-off and on (of course). I will continue to test as this seems frequent but not always easily reproducible. I am wondering if this issue is around the laptop being “cold” - like being shutdown at night and not used for 8-10 hours vs the shutdown testing I just did where the laptop was used. Seems unlikely, but we’ll see.

DisplayLink Driver Upgrade

I upgraded the DisplayLink driver from fedora-43-displaylink-1.14.12-1.github_evdi.x86_64.rpm to fedora-43-displaylink-1.14.14-1.github_evdi.x86_64.rpm

Going forward I plan to try and keep a better eye on DisplayLink driver updates.

Workaround

The workaround of unplugging and plugging back in the dock USBC is not a terrible burden but if there is a more full fix I would be interested.. more testing needed.