Bug 361864

Summary:	System doesn't resume from a "suspend to ram" command after an update with Kubuntu backports 15.10
Product:	[Plasma] Powerdevil	Reporter:	Valter Mura <valtermura>
Component:	general	Assignee:	Plasma Development Mailing List <plasma-devel>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	justin.zobel, nate
Priority:	NOR
Version:	5.5.1
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Valter Mura 2016-04-16 17:49:26 UTC

After the update in subject, when I suspend to ram, first of all the system is redirected to the login windows. After that, I have to click again to the "suspend to ram" button (same behaviour is reproducible if I shutdown the system).
But if I try to turn on the system from the suspension, I get an error prior to the login, something related with video / card.

Reproducible: Always

Steps to Reproduce:
1. click Quit/Suspend (logout and login window appears)
2. click again to Suspend button (suspend to ram mode entered)
3. click Power button to turn on the comp, the system gets an error (no GUI); 

Actual Results:  
The system doesn't come back to the suspension, I need to hard shut down, restarting from Grub.

Expected Results:  
A normal restart is expected

Kubuntu 15.10 with latest backports / Linux-x86_64
KDE Frameworks 5.18.0
Qt 5.5.1
Video Card: Nvidia GeForce GT 640
Video Driver: Nvidia 352.63

By the way, if I try to "shutdown" the system, I get same log out windows and I need to click again the shutdown button from the logout screen, while before the update I got the system normally turned off. If needed, I can attach a "shot" of my screen.

Comment 1 Justin Zobel 2020-11-12 22:55:01 UTC

I've just tested this and I cannot reproduce this issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 2 Bug Janitor Service 2020-11-27 04:33:58 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 3 Valter Mura 2020-11-27 18:47:10 UTC

Hi,

as I'm not using Kubuntu anymore, because I passed directly to KDE Neon, I cannot answer to this old bug.

Suppose it could be safely closed.

Comment 4 Nate Graham 2020-11-28 03:43:51 UTC

Is it still happening to you in Neon?

Comment 5 Bug Janitor Service 2020-12-13 04:33:55 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 6 Bug Janitor Service 2020-12-28 04:35:02 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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