hey IsoLinearCHiP,
In fact, if you set a non existing conffile to gconf, this one will just check
if it exists and ignore it if not. This is done only one on the server side and
so, it's a fast operation.
In addition, it's better to do that at that stage for bootime speed (as
the check will be
The attachment do not set env vars to non-existing files of this bug
report has been identified as being a patch. The ubuntu-reviewers team
has been subscribed to the bug report so that they can review the patch.
In the event that this is in fact not a patch you can resolve this
situation by
** Changed in: gconf (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914102
Title:
Suggestion: do not set gconf env vars to non-existing files
To manage
** Patch added: do not set env vars to non-existing files
https://bugs.launchpad.net/bugs/914102/+attachment/2665362/+files/70gconfd_path-on-session.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
