Bug 7604

Summary:	Suspend works only once through KDE4 (qdbus)
Product:	Mageia	Reporter:	Tamás Hajdu <fathom>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, mageia, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Tamás Hajdu 2012-09-27 20:11:10 CEST

Description of problem:
Suspend works only once through KDE4
pm-suspend from console works always.
Suspend through qdbus only works for the first time.
I am using a thinkpad r61.

Version-Release number of selected component (if applicable):
Cauldron

How reproducible:
Always

Steps to Reproduce:
1. install cauldron
2. suspend/resume with lid close, suspend button or qdbus command
3. Second suspend only locks screen. In dmesg there will be a 
systemd-logind[1047]: Sleep key pressed.
line, but this is all.

Comment 1 Tamás Hajdu 2012-09-28 16:08:07 CEST

Any info you may need to address the issue?

Manuel Hiebel 2012-09-28 22:33:38 CEST

CC: (none) => balcaen.john, mageia, nicolas.lecureuil
Summary: Suspend works only once through KDE4 => Suspend works only once through KDE4 (qdbus)

Comment 2 Tamás Hajdu 2012-10-03 11:48:15 CEST

Problem solved on Cauldron (x86_64) with today's updates, now sleep/resume works fine. 
Seems to be an other problem, but networkmanager says for eth0 and wifi0 that those are not controlled by nm, after a couple of sleep/resume cycle.
May I close this and open a new one or alter this one?

Comment 3 Colin Guthrie 2012-10-03 12:51:40 CEST

For completeness, probably best to clone this bug (or just open a new one and CC the same people), and close this one.

FWIW, I suspect there will be a little bit of fallout from the recent changes with regards to handling of lid closures etc due to systemd-logind changes (i.e. the lower level systems will implement their default behaviour unless higher level systems override them - I suspect the higher levels are, at present, not doing that, so things like lid close behaviour configuration in KDE will likely currently be broken).

The NM issue you mention FWIW I have also seen but after a manual restart of NM service, it's behaved fine for many suspend/resume cycles...

Comment 4 Colin Guthrie 2012-10-04 02:08:10 CEST

FWIW, i've just submitted a new upower that might fix this issue mentioned above.

Comment 5 Colin Guthrie 2012-10-08 21:22:08 CEST

Is this one still an issue? Did the above fix it?

Comment 6 Tamás Hajdu 2012-10-08 21:45:00 CEST

I do not experience it.

Comment 7 Colin Guthrie 2012-10-08 22:02:44 CEST

Cool, I'll resolve it as fixed for now then. If it happens again, please reopen :) Many thanks.

Status: NEW => RESOLVED
Resolution: (none) => FIXED