Bug 975184 - dconf: cannot edit configuration because of dbus-launch failure [NEEDINFO]
dconf: cannot edit configuration because of dbus-launch failure
Product: Fedora
Classification: Fedora
Component: dconf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-06-17 14:38 EDT by Florian Weimer
Modified: 2016-07-19 06:14 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 06:14:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
moez.roy: needinfo? (mclasen)

Attachments (Terms of Use)

  None (edit)
Description Florian Weimer 2013-06-17 14:38:33 EDT
I tried to use dconf to edit .config/dconf/user from a TTY login because the existing configuration prevented GNOME Shell from starting.  However, I could not make any changes because of a dbus-launch failure:

[fweimer@oldenburg ~]$ dconf reset -f  /org/gnome/desktop/a11y/
error: Error spawning command line `dbus-launch --autolaunch=a701a9e30f0346fab6f030a43a13e639 --binary-syntax --close-stderr': Child process exited with code 1

  dconf reset [-f] PATH

Reset a key or dir.  -f is required for dirs.

  PATH      Either a KEY or DIR
  KEY       A key path (starting, but not ending with '/')
  DIR       A directory path (starting and ending with '/')

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Log in on TTY.
2. Run dconf reset -f  /org/gnome/desktop/a11y/.

Actual results:

A dbus-launch error.

Expected results:

The configuration should be changed as requested.

Additional info:

"dconf dump /" works.
Comment 1 Fedora End Of Life 2015-01-09 13:27:40 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Moez Roy 2015-02-15 20:30:50 EST
Was trying to make a live cd and load my old dconf settings into a new user profile like so:

cat oldsettings | dconf load /
Comment 3 Jaroslav Reznik 2015-03-03 09:57:51 EST
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
Comment 4 Fedora End Of Life 2016-07-19 06:14:52 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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