SUMMARY
https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information suggests running `kscreen-console bug`. But on Wayland it prints nothing.

STEPS TO REPRODUCE
1. Run Plasma on Wayland (check Graphics Platform in System Settings > About this System)
2. In a terminal, enter
   kscreen-console bug

OBSERVED RESULT
    QSocketNotifier: Can only be used with threads started with QThread
    kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "(c) 2012 KScreen Team" msgid_plural: "" msgctxt: ""
    ... [6 more kf.i18n: KLocalizedString warnings]
    ========================xrandr --verbose==========================

    ========================Outputs===================================

    ========================Configurations============================

EXPECTED RESULT
Either a nice warning "This tool does not produce useful output when run on the Wayland graphics platform"
    and/or "xrandr program not found, please install it" (see below)
or make it work under Wayland, which would probably require a special interface to KWin bypassing Wayland's client isolation.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8 on Wayland

ADDITIONAL INFORMATION
kscreen-console invokes xrandr, but Fedora 37 KDE spin doesn't even include this X11 program by default. If I install xrandr, I get a lot of output about my XWYAYLAND1 and XWAYLAND2 outputs on Screen 0, so if this output is helpful for debugging maybe kscreen-console could test for xrandr and suggest installing it. Even with xrandr available it still prints nothing under ===Outputs=== and ===Configuration===