Bug 494905

Summary: External monitor enters connect/disconnect loop
Product: [Unmaintained] Powerdevil Reporter: Tim Offereins <tim>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: major CC: natalie_clarius, nate, tim
Priority: NOR    
Version First Reported In: 6.2.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tim Offereins 2024-10-17 03:17:42 UTC
SUMMARY
Logging this under powerdevil as I believe the issue with with supply power to an external monitor.
I have an external (portable) monitor that uses a single USB-C cable for both power/data. Up until the recent release of Plasma 6.2 I have had no issues.
Since the update, I can no longer use the external monitor without additional power supplied directly the the monitor otherwise the system appears to fall into an endless detection loop as the monitor connects/reconnects constantly.

STEPS TO REPRODUCE
1. Plug in external monitor via USB-C


OBSERVED RESULT
Connect/disconnect loop

EXPECTED RESULT
Operation as per Plasma 6.1

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 ร— AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)

ADDITIONAL INFORMATION
Excerpts from journalctl below.
Oct 17 10:54:26 tim-framework plasmashell[1223]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 17 10:54:26 tim-framework plasmashell[1223]: kde.plasmashell: requesting unexisting screen available rect -1
Oct 17 10:54:26 tim-framework plasmashell[1223]: kde.plasmashell: requesting unexisting screen available rect -1
Oct 17 10:54:26 tim-framework plasmashell[1223]: kde.plasmashell: requesting unexisting screen available rect -1
Oct 17 10:54:26 tim-framework plasmashell[1223]: kde.plasmashell: requesting unexisting screen available rect -1
Oct 17 10:54:26 tim-framework systemsettings[2558]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 17 10:54:26 tim-framework kwin_wayland[972]: kwin_core: XCB error: 147 (BadOutput), sequence: 1156, resource id: 1151, major code: 140 (RANDR), mino
r code: 30 (SetOutputPrimary)
Oct 17 10:54:26 tim-framework plasmashell[1223]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Oct 17 10:54:26 tim-framework plasmashell[1223]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Oct 17 10:54:26 tim-framework plasmashell[1223]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Oct 17 10:54:26 tim-framework org_kde_powerdevil[1302]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Oct 17 10:54:26 tim-framework kded6[1151]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_c1_00.6.analog-stereo.monitor"
Oct 17 10:54:26 tim-framework kded6[1310]: xsettingsd: Reloading configuration
Oct 17 10:54:26 tim-framework kded6[1310]: xsettingsd: Loaded 14 settings from /home/tim/.config/xsettingsd/xsettingsd.conf
Oct 17 10:54:26 tim-framework plasmashell[1223]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_c1_00.6.analog-stereo.monitor"
Oct 17 10:54:26 tim-framework plasmashell[1223]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how
 to reproduce.

Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Emitting DDCA_Display_Status_Event(  74.298:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-2, dref: Display_Ref[NU
LL], io_path:/dev/i2c-13]
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Executed 1 registered callbacks.
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Display redetection starting.
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Sleep event. connector=card1-eDP-1, dref not set
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Emitting DDCA_Display_Status_Event(  76.301:  DDCA_EVENT_DPMS_ASLEEP, card1-eDP-1, dref: Display_Ref[NULL], 
io_path:/dev/i2c-11]
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Executed 1 registered callbacks.
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Watch thread terminated.
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Watch thread started
Oct 17 10:54:29 tim-framework org_kde_powerdevil[1302]: Display redetection finished.
Oct 17 10:54:31 tim-framework org_kde_powerdevil[1302]: dh=Display_Handle[i2c-13: fd=143], Replacing adjusted sleep multiplier 0.70 with 1.00 for SE_POS
T_WRITE or SE_POST_SAVE_SETTINGS
Oct 17 10:54:31 tim-framework org_kde_powerdevil[1302]: Sleep event. connector=card1-eDP-1, dref not set
Oct 17 10:54:33 tim-framework org_kde_powerdevil[1302]: Emitting DDCA_Display_Status_Event(  79.131:  DDCA_EVENT_DPMS_ASLEEP, card1-eDP-1, dref: Display_Ref[NULL], 
io_path:/dev/i2c-11]
Oct 17 10:54:33 tim-framework org_kde_powerdevil[1302]: Executed 1 registered callbacks.
Comment 1 Nate Graham 2024-12-12 19:32:08 UTC
What's the brand and model of the external monitor? Is it a Samsung?
Comment 2 Bug Janitor Service 2024-12-27 03:47:23 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Tim Offereins 2025-01-05 05:43:42 UTC
No, not a Samsung.

The brand is UPerfect, using a BOE Display OEM panel.
Model is a UAlly J118.
Comment 4 Tim Offereins 2025-02-13 02:55:30 UTC
(In reply to Nate Graham from comment #1)
> What's the brand and model of the external monitor? Is it a Samsung?

Nate, I can confirm that, somewhere between the original report (6.2) and prior to the release of 6.3, this issue appears to have been resolved.
I used the external monitor again yesterday and did not experience the issue.
Comment 5 Nate Graham 2025-02-18 03:34:12 UTC
Oh great!