Issue 120541

Summary:	Incorrect open/save dialogs type in MATE
Product:	ui	Reporter:	alexls <alexlsh>
Component:	ui	Assignee:	uineedsconfirm <uineedsconfirm>
Status:	CLOSED FIXED_WITHOUT_CODE	QA Contact:
Severity:	Normal
Priority:	P3	CC:	arielch, issues
Version:	current
Target Milestone:	---
Hardware:	PC
OS:	Linux, all
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description alexls 2012-08-11 16:23:45 UTC

I use Ubuntu 12.04 (Precise) with MATE desktop environment. Apache OpenOffice 3.4.0, downloaded from openoffice.org site. OpenOffice in this desktop
environment use incorrect type of dialogs for open/save files (in any
applications: Writer, Calc etc). It can't use "system type" of dialogs, but use
internal dialogs which is very inconvenient and useless for me. All other
programs in this desktop environment are using normal "system" dialogs (for
example text editor or Firefox browser). I often work in OpenOffice and this
bug is very painful to me. 
Please help me to correct this bug. 

PS: Links to MATE desktop environment:
http://mate-desktop.org
https://github.com/mate-desktop

Comment 1 Ariel Constenla-Haile 2012-08-11 16:50:35 UTC

I've no idea what MATE is, but looks like based in Gnome.
Try the following:

* Go to the menu "Tools" - "Options...". In the Options" dialog, select "OpenOffice.org" - "General". Between "Help" and "Document status" you should see a fixed line "Open/Save dialogs" with a check box "Use OpenOffice.org dialog".
If you see this check box, uncheck it, so that you use the system's dialogs instead of OO's.

* If you don't see this option to switch to system's dialogs, then try the following:

- open a terminal
- export these variables:
  export SAL_USE_VCLPLUGIN="gtk";export OOO_FORCE_DESKTOP="gnome"
- execute OO from this terminal:
  /opt/openoffice.org3/program/soffice
- go back to the "Tools" - "Options..." dialog, you may see now the option to use system's dialog

If this worked, add these two lines in ~/.bashrc

export SAL_USE_VCLPLUGIN="gtk"
export OOO_FORCE_DESKTOP="gnome"

this way you don't need to execute OO from a terminal with those variables set.

Comment 2 alexls 2012-08-13 18:39:01 UTC

Thank you for answer.

Yes, MATE is based on GNOME2 codebase.

I have not "Use OpenOffice.org dialog" check box in my OO.
Your second method with environment variables is really work! But when I have added variables to .bashrc it work only if I start OO from terminal. If I start OO from menu or open a file in OO then I see internal OO dialogs again. How better to do that to OO always use system dialogs like when I start it from terminal with environment variables?

Comment 3 Ariel Constenla-Haile 2012-08-13 19:01:02 UTC

(In reply to comment #2)
> Thank you for answer.
> 
> Yes, MATE is based on GNOME2 codebase.
> 
> I have not "Use OpenOffice.org dialog" check box in my OO.
> Your second method with environment variables is really work! But when I
> have added variables to .bashrc it work only if I start OO from terminal. If
> I start OO from menu or open a file in OO then I see internal OO dialogs
> again. How better to do that to OO always use system dialogs like when I
> start it from terminal with environment variables?

Please see http://askubuntu.com/questions/121073/why-bash-profile-is-not-getting-sourced-when-opening-a-terminal

The answer says to add variables in ~/.profile if you want them when you log in graphically. Not sure if this works. On Fedora there is no need for this file, ~/.bashrc is sources when log in graphically, via ssh, when opening a terminal in graphical mode, etc.

Comment 4 alexls 2012-08-13 19:18:26 UTC

Yes, it's works! When I have added environment variables to ~/.profile OO always use system type of dialogs.
Your information is very helpful for me. Thank you very much.

Comment 5 Ariel Constenla-Haile 2012-08-13 19:33:17 UTC

(In reply to comment #4)
> Yes, it's works! When I have added environment variables to ~/.profile OO
> always use system type of dialogs.
> Your information is very helpful for me. Thank you very much.

You are welcome.
I'll close the bug as fixed.
In the meantime, I've found what may be the root cause.