Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On 03/03/2012 at 07:24, Arnaud Champollion <> 


It works fine with

export OOO_FORCE_DESKTOP=gnome

Great :) .

I guess I have to do it on other user sessions.

If you have more than one user on that machine, you can simply create new file 
in /etc/X11/Xsession.d/ directory (you will need root privileges to do that). 
Name it, for example, "10LibreOffice" and place that export line in it.

/etc/X11/XSession (which LightDM invokes) script will read all files in 
/etc/X11/Xsession.d/ directory every time someone logs in.

It's important to read that file read before 40x11-common_xsessionrc script, 
otherwise XSession will read users' .xsessionrc (which may force LO desktop to 
KDE or generic) and then overwrite it with GNOME. We don't want that.

You can see order in which files will be read by running command:
  run-parts --list /etc/X11/Xsession.d/

Thank you for your help. I'm going to post the problem on the 
developpers mailing list. 

I think that there are two problems:
1. LO can't recognize MATE as GTK-based environment.
2. Variable name suggest it's OpenOffice related, while it's for LibreOffice (and 
OpenOffice by the way). Maybe this way it is fine, maybe it should change.
Best regards
Mirosław Zalewski

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.