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 791597 - [3.27.3] crashes on startup
[3.27.3] crashes on startup
Status: RESOLVED FIXED
Product: dconf-editor
Classification: Other
Component: general
3.27.x
Other Linux
: Normal normal
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
: 790692 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-12-13 21:52 UTC by Dominique Leuenberger
Modified: 2017-12-15 04:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2017-12-13 21:52:43 UTC 
Seen by openSUSE's openQA, based on the 'GNOME Next' live images:
https://openqa.opensuse.org/tests/559207#step/dconf_editor/26

dconf-editor segfaults upon startup

A stacktrace looks like this:

(gdb) bt

+ Trace 238257

  • #0 g_type_check_instance_cast
    at gtype.c line 4052
  • #1 0x000055555556c9ed in
  • #5 <emit signal ??? on instance ???>
    at gsignal.c line 3447
  • #6 g_application_register
    at gapplication.c line 2069
  • #7 g_application_real_local_command_line
    at gapplication.c line 1009
  • #8 g_application_run
    at gapplication.c line 2371
  • #9 configuration_editor_main
  • #10 __libc_start_main
  • #11 _start 






Comment 1


Arnaud B.





          2017-12-14 08:37:34 UTC
        



Thanks for the bug report. My understanding of traces are quite bad, but I have the feeling it’s the same problem as bug 790692, caused by a well-defined commit[1] (that enables checking the SettingsBackend). I just tried something[2] not to remove the ckeck, considering `dconf-editor` as a specialized application that must deal with this kind of things, but I might change my mind until stable release and just remove all. But for now, does that work better?

Regards,
Arnaud

[1] https://git.gnome.org/browse/dconf-editor/commit/?id=ef79c635bb24cbe4e2a2383740fa56be77dd7f6f
[2] https://git.gnome.org/browse/dconf-editor/commit/?id=e45a5762e3c6af22ff5e689db712206dbbd3a7bf






Comment 2


Dominique Leuenberger





          2017-12-14 21:42:58 UTC
        



Tested with commit https://git.gnome.org/browse/dconf-editor/commit/?id=e45a5762e3c6af22ff5e689db712206dbbd3a7bf applied on top of my source rtree - the crash remains






Comment 3


Dominique Leuenberger





          2017-12-14 22:22:04 UTC
        



Ad definitively related to [1]: when disabling the test_backend call in startup() dconf-editor starts up just fine.

[1] https://git.gnome.org/browse/dconf-editor/commit/?id=ef79c635bb24cbe4e2a2383740fa56be77dd7f6f






Comment 4


Arnaud B.





          2017-12-15 04:29:18 UTC
        



I just disabled the SettingsBackend stuff, so that’s fixed. The current cycle is big enough not to add this kind of broken stuff.

I just don’t understand what I’m doing wrong. It’s certainly my fault, but I don’t understand. Anyway, thanks for the bug report!






Comment 5


Arnaud B.





          2017-12-15 04:30:43 UTC
        



*** Bug 790692 has been marked as a duplicate of this bug. ***