Also, for completeness. The output plugging the usb c to HDMI adapter into the problematic port:
Nov 11 00:37:41 sf-latitude kernel: usb 3-2: new low-speed USB device number 25 using xhci_hcd
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: No LPM exit latency info found, disabling LPM.
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: New USB device found, idVendor=343c, idProduct=0000, bcdDevice= 0.00
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: Product: USB Type-C Digital AV Adapter
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: Manufacturer: xxxxxxxx
Nov 11 00:37:42 sf-latitude kernel: usb 3-2: SerialNumber: 000000000000
And the output from plugging that cable into the non-problematic port:
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: new low-speed USB device number 26 using xhci_hcd
Nov 11 00:39:49 sf-latitude systemd[1]: Rotate log files was skipped because of an unmet condition check (ConditionACPower=true).
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: No LPM exit latency info found, disabling LPM.
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: New USB device found, idVendor=343c, idProduct=0000, bcdDevice= 0.00
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: Product: USB Type-C Digital AV Adapter
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: Manufacturer: xxxxxxxx
Nov 11 00:39:49 sf-latitude kernel: usb 3-1: SerialNumber: 000000000000
Nov 11 00:39:50 sf-latitude niri[1995]: 2025-11-11T05:39:50.700973Z DEBUG niri::backend::tty: device changed: 57857
Nov 11 00:39:50 sf-latitude niri[1995]: 2025-11-11T05:39:50.778997Z DEBUG niri::backend::tty: new connector: DP-1 "PanaScope Pixio PX248P 0x00000001"
Nov 11 00:39:50 sf-latitude niri[1995]: 2025-11-11T05:39:50.779066Z DEBUG niri::backend::tty: connecting connector: DP-1
Nov 11 00:39:50 sf-latitude niri[1995]: 2025-11-11T05:39:50.779082Z DEBUG niri::backend::tty: picking mode: Mode { name: "1920x1080", clock: 148500, size: (1920, 1080), hsync: (2008, 2052, 2200), vsync: (1084, 1089, 1125), hskew: 0, vscan: 0, vrefresh: 60, mode_type: ModeTypeFlags(PREFERRED | DRIVER) }
Nov 11 00:39:50 sf-latitude niri[1995]: 2025-11-11T05:39:50.783029Z DEBUG niri::niri: putting output DP-1 at x=3286 y=0
Sure, was there a specific section you would want? This is the Graphics sections while the usb c to displayport cable is plugged into the problematic port
just checking as can rule out things, have you tried to use i3, openbox etc? I usally have one or other just in case. they will be barebones but handy to riule things out.
Not yet, I actually only have wayland compositors installed, but I will try other WM/DEs now and see if anything changes. Though, normally when I boot into my laptop the TTY displays on both monitors and now it only displays on the laptop when using the troublesome port
So this did work, kind of, thank you smokey! I say kind of because I am unsure of what exactly changed to solve the issue, or if the issue will remain resolved, but I will detail what I did in steps that led to the usb port working for displays again. I will include things that are likely not important since I am unsure of what is actually important.
Starting point: I am in a niri session with my external monitor connected via a functioning hdmi port built into the laptop.
Edit the default .xinitrc to start openbox. Changing the last line from exec “$xterm” -geometry 80x66+0+0 -name login to exec openbox-session
Exit niri into the tty
Install openbox
Enter startx in the tty
Openbox starts and is displayed on both monitors
Remove the HDMI cable and plug the usb c to displayport cable into the problematic port
The external monitor goes black and enters sleep mode
Logout of the openbox session back to the tty
The external monitor comes back on and is now mirroring the display
From then on the cable and port have functioned as they used to. I have unplugged the cable and plugged it back in and it works the same. I have also restarted the laptop and it functions as expected. If the issue comes up again soon I will come back to this thread (if that is what standard practice is).
Thanks to everyone who spent their time helping me. I am unsure of what is considered good manners on this forum so for now I will mark this post as the solution in case anyone stumbles upon a similar issue. Please let me know if this is improper.