Bug 526128 - OOo doesn't know which workspace to open on
Summary: OOo doesn't know which workspace to open on
Keywords:
Status: CLOSED DUPLICATE of bug 474875
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-28 23:18 UTC by morgan read
Modified: 2009-09-29 08:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-29 08:48:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description morgan read 2009-09-28 23:18:19 UTC
Description of problem:
I'm running Compiz, so if the bugs with that component please re-assign.
When I open a document in OOo it (apparently) randomly but often doesn't open on the workspace from which I opened the document, but instead seems to default to workspace 1 - this is very very disturbing

Version-Release number of selected component (if applicable):
Been occuring for a while, but
$ rpm -q openoffice.org-core
openoffice.org-core-3.1.1-19.2.fc11.i586

How reproducible:
Apparently random but often

Steps to Reproduce:
1. Open OOo file on workspace other then workspace 1
2. Window for file opened opens on workspace 1 
3.
  
Actual results:
Document open on an unexpected workspace

Expected results:
Document open on expected workspace

Additional info:

Comment 1 David Tardon 2009-09-29 06:57:39 UTC
I see no problem with openoffice.org-3.1.1-19.9.fc12.x86_64 and compiz-0.8.2-15.fc12.x86_64 . openoffice.org in Rawhide is nearly the same as in F-11 and none of the additional patches touches code for interaction with WM, therefore I'm reassigning the issue to compiz.

Comment 2 Caolan McNamara 2009-09-29 08:48:32 UTC
I have a standalone demo attached to issue 474875 for this

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


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