Bug 435834

Please provide ~/.local/share/sddm/wayland-session.log after you reproduce it with the environment variable
QT_LOGGING_RULES="kwin_*.debug=true;kwin_libinput.debug=false"
set.
The output of drminfo could also be useful (when it works and when it's broken)

Created attachment 137945 [details]
Wayland Session LOG file

As per your request, here is my Wayland-session log file

NOTE: I dont personally deal with environment variables myself, so Im not able
to provide any info for you about any of them

If you want such info, you will have to provide a step-by-step procedure for
me to follow in order to get such info for you

Also TERMINAL did not recognise any such command as drminfo


--- Comment #1 from Zamundaaa <xaver.hugl@gmail.com> ---
Please provide ~/.local/share/sddm/wayland-session.log after you reproduce it
with the environment variable
QT_LOGGING_RULES="kwin_*.debug=true;kwin_libinput.debug=false"
set.
The output of drminfo could also be useful (when it works and when it's broken)

You can set the environment variable for example by putting it in /etc/environment
Just open that file with kate, add
QT_LOGGING_RULES="kwin_*.debug=true;kwin_libinput.debug=false"
in a new line, save it and reboot. Then reproduce the bug and upload the file again

Created attachment 138086 [details]
Wayland LOG file immediately after BUG reproduced

This is a second Wayland LOG file
Zamundaaa I added the Environment variable as you requested to the /etc/environment files, and re-booted the PC
I then reproduced the BUG as per my description, and then immediately
uploaded this new wayland-session.log file (i did NOT log out of KDE Plama before-hand)

This is a rather late "thank you" to the devs who were finally able to have this bug/s fixed when
KDE Plasma 5.22 came out - it was fantastic :)
Seriously when you have 3 monitors all-in-a-row and one is your main TV monitor in front of the bed
to watch stuff, turning the other 2 monitors off by simply pressing their power buttons really
does not things visually better and its quick

Unfortunatley it seems that this problem is back again, just recently

MY CURRENT OS INFO:

Operating System: openSUSE Tumbleweed 20210713
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.13.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD PITCAIRN


It should be stated that i had this problem PRIOR to this kernel (and other hardware firmware/driver updates) as well

Please tell me what logs you would like me to upload here

INFO:

The Main 32" Desktop Monitor (PRIMARY = i.e. Has Icons and a Taskbar on it) when turned off and then back on again
becomes completely black, and in the middle of the screen displays one of the the standard Audio Volume Device output
Mouse pointer does still move freely around onto any/all monitors as i wish

If a new bug report is to be made/submitted - please let me know as well, Thank you
Im using the SDDM Option in opensuse tumbleweed called Wayland - Im 100% positive that this is XWayland
as my SeaMonkey Browser does not run at all using True native "Full Wayland"
NOTE: Due to 'name change issues' on opensuse tumbleweed there is now only one actual option at the moment for the SDDM boot up menu, which is now just called "Wayland"

Was the only thing that changed between it working and not, Plasma updating to 5.22.3 or was there a kernel update involved as well?

The only information you can really provide is the wayland log again; unfortunately I'm not sure if there even is much information to get with such old drivers.

Created attachment 140382 [details]
Wayland LOG file - Before issue

Wayland LOG file - Before issue

Created attachment 140383 [details]
Wayland LOG File Immediately AFTER monitor Bug Reproduced (no reboot or logout)

Wayland LOG File Immediately AFTER monitor Bug Reproduced (no reboot or logout)

Just performed 189 packages upgrade & Upgraded to latest kernel:

KINFO:

Operating System: openSUSE Tumbleweed 20210803
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.13.6-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD PITCAIRN


Problem still exists under KDE Plasma Wayland

Can you still reproduce it with Plasma 5.24.5 or with the beta of 5.25?

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

(In reply to postix from comment #10)
> Can you still reproduce it with Plasma 5.24.5 or with the beta of 5.25?

Sorry for the delay, technically i dont know if this issue still persists(In reply to postix from comment #10)
> Can you still reproduce it with Plasma 5.24.5 or with the beta of 5.25?


Sorry for my delay
A few months ago, i had taken my video card out of my PC altogether, was instead was using the PC's own VGA output for my main primary monitor
However, i felt it important to retry to see if this bug still existed

I can say, with happiness and glee, that it's finally fixed
I can turn the main primary monitor off and on again (HDMI by Video card) and all monitors display perfectly fine
no anomolies detected

Thank You :)