Bug 203470

Summary:	shutdown vs. lid close -- incorrect priorities
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	macias - <bluedzins>
Component:	Basesystem	Assignee:	Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	aj
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description macias - 2006-09-02 19:09:18 UTC

Dell Latitude D610, SuSE Linux 10.0. KDE 3.5.4.

I set "on lid close" to "suspend to RAM". Now, I shutdown the system, KDE shuts down, back to console, I am to eager to wait so I close the notebook and... system is not shutted down but suspended!

I consider it as a bug since in this situation the intention was clear -- I am packing up, I want to get my notebook to my backpack, obviously not in suspend mode. Otherwise I would just close the lid.

Comment 1 Andreas Jaeger 2006-09-12 08:58:13 UTC

I'm confused by your report.

You say "shutdown" and get suspend?  ARe you sure you hit the right button?

Is this reproduceable?

Comment 2 macias - 2006-09-12 09:36:43 UTC

(In reply to comment #1)
> I'm confused by your report.

In what way? My English?

> You say "shutdown" and get suspend?  

No. I say "shutdown" AND _close the lid_ before it is shutted down ==> I get suspend. Wrong priority -- suspending should check if shutting down is not in progress.

>ARe you sure you hit the right button?

Yeah, I have only one ;-D

> Is this reproduceable?

Every time I want to get the described effect.

Comment 3 Andreas Jaeger 2006-09-12 09:49:25 UTC

You interrupted the shutdown process with the suspend request.  Ok, now understood.

Comment 4 Forgotten User ZhJd0F0L3x 2006-09-12 13:19:33 UTC

this is fixed in 10.1. If we want an update for 10.0 for this issue, it might be possible.

*** This bug has been marked as a duplicate of bug 118823 ***