Bug 615924

Summary:	Test case failure: gnome-session-save
Product:	Red Hat Enterprise Linux 6	Reporter:	Radek Lat <rlat>
Component:	gnome-session	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED NOTABUG	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-07 12:38:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Radek Lat 2010-07-19 09:38:37 UTC

Filed from caserun (https://tcms.engineering.redhat.com/case/34714/?from_plan=2145)

Version-Release number of selected component (if applicable):
RHEL6.0-Snapshot-7

Steps to Reproduce: 
 1. Install konsole.
 2. Log in to gnome

 1. Create 3 konsole windows
 2. run "gnome-session-save" in terminal 
 3. Log out and then log back in

Actual results: 
None of the three konsole windows comes back.

Expected results:
After the step 5,all three konsole window would come back.

Comment 2 RHEL Program Management 2010-07-19 09:57:51 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Ray Strode [halfline] 2010-07-19 15:08:20 UTC

This sounds somewhat like bug 484431 but for rhel6 instead of rhel5 (of course it's a different code base, so the root issue may be different)

Comment 4 Radek Lat 2010-09-07 12:38:27 UTC

It was actually wrongly specified test case. gnome-session-save does not save current session (at least according to its manual page) thus this behaviour is expected.