Bug 848457 – Seamonkey ignores start workplace with windowmaker

Bug 848457 - Seamonkey ignores start workplace with windowmaker

Summary:	Seamonkey ignores start workplace with windowmaker

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	seamonkey (Show other bugs)
Sub Component:
Version:	17
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Martin Stransky
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-08-15 12:20 EDT by Peter Scott
Modified:	2012-08-16 07:28 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-08-16 07:28:02 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Peter Scott 2012-08-15 12:20:35 EDT

Description of problem:
Seamonkey ignores the start workplace with windowmaker

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

How reproducible:
100%

Steps to Reproduce:
1.select "Attributes" from windowmaker titlebar; select "Icon and initial Workspace"; choose a workspace; "apply"; save
2.quit seamonkey
3.go to a different workspace
4. start seamonkey
  
Actual results:
Starts on the current workspace

Expected results:
Should start on the specified workspace

Additional info:
This occurs (more than once in WMWindowAttributes:

  Navigator.SeaMonkey = {
    StartWorkspace = Browsing;
  };

Comment 1 Martin Stransky 2012-08-15 16:41:30 EDT

Does it affect seamonkey only or is that bug common for all mozilla apps (firefox/thunderbird)?

Comment 2 Peter Scott 2012-08-15 17:47:16 EDT

Seamonkey only. Firefox is OK

Comment 3 Peter Scott 2012-08-16 07:28:02 EDT

I gave the wrong Version-Release it should have been 2.8.

2.11 is OK and does not have this bug.

I'm closing this bug but don't know what reason to give so I'm leaving it at NOTABUG (WASABUG!)

Sorry for wasting people's time.

Note You need to log in before you can comment on or make changes to this bug.