Bug 427299

Summary: Wake up fails after suspending when monitor attached.
Product: [Plasma] plasmashell Reporter: vali53611
Component: Lock/logout widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: major CC: kde, plasma-bugs-null
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description vali53611 2020-10-03 16:28:40 UTC
SUMMARY
Hello I have a monitor attached to my laptop and when I run sleep or hibernate, it tries to sleep (monitors go black etc.) but then it stops and I can see some lights of my laptop is still on. When I try to wake it up, it doesn't respond the keys nor commands.


STEPS TO REPRODUCE
1. Have a monitor attached.
2. Run sleep or hibernate. (Preferrably from the kickoff menu)

OBSERVED RESULT
I used "systemctl suspend" & "systemctl hibernate" commands and they worked perfectly.

I also detached my monitor to see if it affects anything. It turned out to be yes. Sleep and hibernate worked exactly as I intended.

EXPECTED RESULT
Sleeping or hibernating properly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Opensuse 15.2
KDE Plasma Version: (Plasmashell) 5.18.5
KDE Frameworks Version: 5.71.0
Qt Version: (libQt... stuff) 5.12.7

ADDITIONAL INFORMATION
My laptop is hp pavilion dv6-2065et. I have 8gb of ram and 240gb ssd. My Graphics card is Gtx 230M. At the time being my system is up to date.

I have found these two bug reports (https://bugs.kde.org/show_bug.cgi?id=421284 & https://bugs.kde.org/show_bug.cgi?id=376562). They both have similarities with my report (Especially first one).
Comment 1 vali53611 2020-10-03 16:51:33 UTC
Btw I forgot to mention that I use Opensuse Leap 15.2 and my drivers are nouveau.
Comment 2 David Edmundson 2020-10-03 17:26:22 UTC
Anything in journalctl from the whole situation?

does switch VT's control+alt+F2 work?
Comment 3 vali53611 2020-10-04 11:25:18 UTC
(In reply to David Edmundson from comment #2)
> does switch VT's control+alt+F2 work?
Unfortunately not.

> Anything in journalctl from the whole situation?
The problem is that laptop freezes and it requires me to manually shut it down. And that resets the journalctl.

Today however, because I unplugged and replugged the HDMI cable yesterday, it stopped freezing then screen went black, but I could see the mouse, and after a couple of seconds lock screen opened. Same thing happened with the hibernate and systemctl commands. And I didn't see anything extraordinary in the journalctl. (Only timings was one after another)

Because of this I made some tests.

1- Started the computer twice first with closed and second with an open lid. (Affect nothing)
2- Started with open lid then when splash screen came closed the lid, logged in. (Fixed the problems but after starting the computer again it was still the same situation that I described now)
3- Started the computer with close lid, logged in then unplugged & replugged the HDMI, lid was still closed. (I ended up with yesterday's situation)
4- Started the computer with close lid, logged in after that opened the lid and unplugged & replugged the HDMI. (Fixed the problems)
5- After from the last operation I turned off the computer and reopened it. This time lid was open and I logged in. Unplugged the HDMI. It went unnoticed, laptop monitor was still black, so I replugged the cable and my external screen came back. (It slept and hibernated properly)
6- I tested fifth operation again to see if it is continuous. This time it was noticed. And even though there are not freezes it is still not working properly. (The same result with "-2")
Comment 4 Bug Janitor Service 2020-10-19 04:33:18 UTC
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!
Comment 5 vali53611 2020-10-19 05:54:16 UTC
I want to mention that in the previous comment that I've sent fixes was temporary.
Comment 6 vali53611 2020-11-27 14:56:02 UTC
I recently switched from OpenSuse Leap 15.2 to KDE Neon (Neon [User edition] 20.04 focal) and this + other issues that i didn't mentioned here are resolved. One of them was splash screen. Even though, displayed correctly afterwards, it wasn't initializing correctly.

With the switch, everything become smoother, and better. OpenSuse was the one that causing problems. (I think it couldn't recognize the external monitor correctly)

I really like KDE. It is an incredible DE. Keep up the good work.