After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 788460 - add command-line option for key to show
add command-line option for key to show
Status: RESOLVED FIXED
Product: dconf-editor
Classification: Other
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-10-03 09:15 UTC by Ildar
Modified: 2019-02-22 07:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ildar 2017-10-03 09:15:00 UTC
e.g. $ dconf-editor /org/gnome/settings-daemon/plugins
should show the window navigated to the key
Comment 1 Arnaud B. 2017-10-05 15:42:25 UTC
Yes, that’s the spirit of the current UI. I’ve pushed a patch that does part of the job [1], even if it is not perfect: the goal would be to always open a new window on the given path even when there’s already a window opened, to not interfere (notably) with modifications not validated; but dconf-editor only supports one window for now and for the times to come (it needs a better UI for multiple windows). I close the bug, as the usual case works, and the corner case are handled by cli notifications. Thanks for reporting!

[1] https://git.gnome.org/browse/dconf-editor/commit/?id=febde42643fd914a012571701757e8036318817d
Comment 2 Ildar 2018-04-12 06:47:35 UTC
have a bad news here. I finally got the version with this feature. But it crashes for `ru`  locale like this:
> $  LANG=C dconf-editor /org/gnome/settings-daemon/plugins
> ... WORKS!!!
> $  LANG=ru_RU.UTF-8 dconf-editor /org/gnome/settings-daemon/plugins
> Ошибка сегментирования

Backtrace:
(gdb) bt
  • #0 strlen
    from /lib64/libc.so.6
  • #1 g_strdup
    from /lib64/libglib-2.0.so.0
  • #2 configuration_editor_real_command_line
    at editor/dconf-editor@exe/dconf-editor.c line 987
  • #3 ffi_call_unix64
    from /usr/lib64/libffi.so.6
  • #4 ffi_call
    from /usr/lib64/libffi.so.6
  • #5 g_cclosure_marshal_generic_va
    from /usr/lib64/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib64/libgio-2.0.so.0
  • #10 ??
    from /usr/lib64/libgio-2.0.so.0
  • #11 g_application_run
    from /usr/lib64/libgio-2.0.so.0
  • #12 configuration_editor_main
    at editor/dconf-editor@exe/dconf-editor.c line 240
  • #13 __libc_start_main
    from /lib64/libc.so.6
  • #14 _start
    at ../sysdeps/x86_64/start.S line 120

Comment 3 André Klapper 2018-04-12 07:38:42 UTC
Ildar: Please file a separate task for that separate issue, and include a stacktrace with debug symbols. Thanks.
Comment 4 Arnaud B. 2018-04-13 04:03:07 UTC
I have currently problems with building sanely (testing a beta release), but looks like I have here a crash with “LANG=C” and no crash with “LANG=ru_RU.UTF-8”. I reopen to investigate, thanks for the bug report.
Comment 5 Arnaud B. 2019-02-21 20:30:40 UTC
I think that has been fixed at one point (commit 5664d22d?), and I cannot make it crash anymore, so closing again. If you can reproduce the bug, please open an issue on Gitlab. Thanks!
Comment 6 Ildar 2019-02-22 07:08:03 UTC
Thanks a lot!