FS#42653 - [libreoffice-fresh] gconf support.

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Saturday, 01 November 2014, 22:50 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 07 February 2015, 11:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Since gnome-desktop doesn't use gconf anymore, doesn't make sense to drop the gconf support? (yes, I know it is optional but it is linked against nevertheless)
It is not being used anyway.
This can be done with --disable-lockdown --disable-gconf. I think lockdown support is still on gconf too so may as well disable it.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 07 February 2015, 11:06 GMT
Reason for closing:  Fixed
Comment by Ross Lagerwall (rosslagerwall) - Monday, 02 February 2015, 18:22 GMT
This is not optional anymore in the latest testing builds.
Comment by Hussam Al-Tayeb (hussam) - Tuesday, 03 February 2015, 20:04 GMT
I just feel that since gnome-desktop doesn't actually use gconf anymore, it is pointless for libreoffice to link against gconf to be able to read gnome-desktop's gconf settings from a gnome2 installation. same with lockdown support since it also looks for settings through gconf.
We are linking against a library that we don't use anymore.
Comment by Andreas Radke (AndyRTR) - Thursday, 05 February 2015, 06:50 GMT
This should be the upstream bug: https://bugs.documentfoundation.org/show_bug.cgi?id=41678

In LibO git I couldn't get anything usefull from searching commit messages including "gconf" or "lockdown".
What LibO features read gconf keys? Do you have a full git checkout to grep?

I tend to drop gconf support using "--disable-lockdown".
Comment by Andreas Radke (AndyRTR) - Thursday, 05 February 2015, 06:59 GMT
http://markmail.org/message/dx43thjzhcnp6m3l - http://cgit.freedesktop.org/libreoffice/core/tree/shell/source/backends/gconfbe/gconfaccess.cxx

Reading gconf settings seems to give only minor advantages for gnome users taking over a few settings (username, userpath, proxy settings).
Not sure what this lockdown is all about. I guess some network shared file locking. No idea why this is done in the app an not in the nfs/cfs (gvfs) client.
Comment by Hussam Al-Tayeb (hussam) - Thursday, 05 February 2015, 09:26 GMT
lockdown is likely for gnome's sabayon utility https://git.gnome.org/browse/sabayon/ (which I can't find in git anymore)
http://ftp.gnome.org/pub/gnome/sources/sabayon/ which appears to have not been ported to gnome3.

Also the settings (username, userpath, proxy settings) are in a gconf settings database which doesn't exist unless as remainder from an old gnome2 installation.

Loading...