https://bugs.kde.org/show_bug.cgi?id=510988
Bug ID: 510988
Summary: Allow manual rescan/discovery of external TB4 monitors
connected via thunderbolt hubs from system tray or
notification widget/display
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 186065
--> https://bugs.kde.org/attachment.cgi?id=186065&action=edit
simple rescan bash script that should work for most situations, it should be
invoked from system tray
Assume TB4/TB5 or USB-C / Display port alternative mode monitors are connected
to TB4/TB5 hubs (passive or active) such as
https://www.amazon.co.uk/dp/B0CT2HZ1ZY
When laptop goes to sleep and resumes most often monitors come to live as well,
but sometimes when hub itself goes to sleep , it is not always the case. It is
not an easy and user friendly way to trigger USB-C retrain of the links to
monitors. One way is to disconnect hub from both the laptop and hub from power
supply and connect again to both.(Disconnecting monitors from hub and
connecting does not help itself.) Sometimes even disconnecting hub does not
help , because OS/linux will not initiate new connection. Manual rescan is a
great fallback and it should be in Task bar / Status and Notification /Display
configuration or in a new section Thunderbolt.
This is to allow users out of the box user friendly experience (following Steve
Jobs mantra "It just works out of the box") without letting users figure
themselves how to tackle the problem.
See attached shell script that works for me. It would be great to trigger
execution of it from task bar/Status notification and right click on Display
configuration, at the place where "Enable presentation mode" is.
The script is generic and should work for all others , it should be executed
under elevated privileges (sudo) or suid bit set. f
It should be investigated how other devices (not just monitors react to this
rescan). For example if external disk is connected to TB4/TB4 hub and IO
operations (writing) are in progress ,etc. If you can detect automatically that
only monitors are connected , then it is definitely safe to use it. In other
situations you can warn users.
***
Note that hooking the script automatically as a resume script is pointless,
because most of the time the monitors resume well. And script would add like 5
undesirable seconds to initiation. Manual fallback rescan is preferable.
ADDITIONAL INFORMATION
Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.17.0-rc6-toeirei-ec (64-bit)
Graphics Platform: Wayland
Processors: 12 × 13th Gen Intel® Core™ i7-1355U
Memory: 40 GiB of RAM (38.9 GiB usable)
Graphics Processor: Mesa Intel® Iris® Xe Graphics
Manufacturer: Notebook
Product Name: L140AU
--
You are receiving this mail because:
You are watching all bug changes.
