Bug 393649

Summary:	Monitor reports no signal if turned off and back on with wayland session
Product:	[Plasma] kwin	Reporter:	rafael
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	herzenschein, kde, mspehar, subdiff
Priority:	NOR	Flags:	kde: Wayland+ kde: X11-
Version:	git master
Target Milestone:	5
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	info when running x11 info when running wayland

Description rafael 2018-04-29 18:17:59 UTC

This is using plasma-workspace-wayland 4:5.12.4-0ubuntu3

When using a X session I can power cycle the monitor and everything works.

With a wayland session the monitor says there is no signal once it is turned back on. I can switch to a virtual terminal (C-A-Fx) and doing so brings the monitor to life. Trying to switch back to wayland (C-A-F1) drops the signal again.

The monitor is a dell up3216q
The video card is a intel 5927.

Comment 1 Roman Gilg 2018-04-30 13:50:37 UTC

I experienced similar issues in the past with some monitor models. Pls also add here the info from a call to: qdbus org.kde.KWin /KWin supportInformation

Comment 2 rafael 2018-05-07 00:19:49 UTC

Created attachment 112453 [details]
info when running x11

Comment 3 rafael 2018-05-07 00:20:15 UTC

Created attachment 112454 [details]
info when running wayland

Comment 4 Miroslav Spehar 2018-07-06 07:21:27 UTC

By turn-off i believe you meant when system turns off monitor after 5min of inactivity? If so, i have a similar issue, but on opensuse tw i couldn't even activate tty.

Reported the issue here:

https://bugzilla.opensuse.org/show_bug.cgi?id=1096816

And here is the journal extract for relevant period:

https://bugzilla.opensuse.org/attachment.cgi?id=776295

Just guessing here, but could here also be problem with sddm? I could remotely shutdown the pc since sshd was working, but during shutdown it says "shutting down sddm" and then waits for timeout.

Comment 5 Roman Gilg 2018-07-08 07:58:43 UTC

Btw can you check from the virtual terminal if the KWin process is still running and get a trace of the last calls it did.

Comment 6 Miroslav Spehar 2018-07-08 11:40:12 UTC

(In reply to Roman Gilg from comment #5)
> Btw can you check from the virtual terminal if the KWin process is still
> running and get a trace of the last calls it did.

i opened a new bug since description when it happens is a bit different

https://bugs.kde.org/show_bug.cgi?id=396272

backtrace is attached there

Comment 7 Thiago Sueto 2021-01-29 21:12:25 UTC

Hello, is this issue still reproducible for you on current Plasma?
I didn't manage to reproduce this.
I tried manually turning my external monitor off and on, although I lack the same hardware.

Comment 8 rafael 2021-01-30 03:03:29 UTC

(In reply to Thiago Sueto from comment #7)
> Hello, is this issue still reproducible for you on current Plasma?
> I didn't manage to reproduce this.
> I tried manually turning my external monitor off and on, although I lack the
> same hardware.

I am sorry, I no longer have that particular hardware to try to reproduce this issue.

Comment 9 David Edmundson 2023-01-17 13:06:51 UTC

Please report if it's still an issue on newer Plasma