Bug 215279

Summary:	login takes too long after resuming from RAM
Product:	[I don't know] kde	Reporter:	Jiri Kanicky <jirik>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	j
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jiri Kanicky 2009-11-19 14:06:06 UTC

Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Environment
============
Notebook Lenovo x61
Debian Unstable
Root partition and swap runs on encrypted partitions (LUKS).

Repro Steps
=============
I have eth0 or wlan0 up with IP from DHCP
I suspend to RAM or DISK
I disconnect cable from NIC.
I resume notebook without cable attached.
Login screen comes up immediately.
After typing login details and hitting enter it takes more then 1 minute to resume the desktop.

Troubleshooting
=================
If I take down the network interface (eth0, wlan0) before the suspend, resume is fast and normal.

I can't see any specific errors or I do not know where to look. I am not sure where is the problem.

Additional details
==================
It seems like the disconnected network interface is causing the issue.

Comment 1 Andrew Crouthamel 2018-11-02 23:05:09 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

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

Comment 2 Andrew Crouthamel 2018-11-16 05:31:01 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

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

Comment 3 jerrys 2018-11-16 17:56:36 UTC

I believe we can close this ticket as I dont experience the issue anymore in latest version.