Can’t get dconf-editor to load on leap 15.6. It is throwing segmentation faults. See below:
base) tom@mydesktop: ~ $ dconf-editor
Segmentation fault (core dumped)
(base) tom@mydesktop: ~ $
I have removed dconf files listed by yast-software and reinstalled a couple of times with no effect. I think this is first time I tried dconf on leap 15.6. Did work on 15.5.
dconf command by itself launches help file and seems to be running.
Anyone having any problem with dconf-editor?
tom kosvic
Hello @tckosvic ,
I used dconf editor when I first installed Leap 15.6 to modify my tracker configuration. No problems! I just now tested again, changed a value in gweather. No problem!
It should not, and probable does not, matter, but are you running on wayland or X11?
Cheers
Hello again @tckosvic ,
The only thing I can think of that might be causing this for you and not me is a bad schema somewhere. Try “dconf-editor --list-relocatable-schemas” and see if works. This won’t open a graphical window.
Ok, so it is my system that is problem.
Ran your suggestion. Don’t know what I am looking for but results are below.
base) tom@mydesktop: ~ $ dconf-editor --list-relocatable-schemas
Known schemas installed:
org.gnome.Terminal.Legacy.Profile
ca.desrt.dconf-editor.Bookmarks
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding
org.gnome.seahorse.window
org.gnome.Reversi.Lib
org.mate.panel.object
org.gnome.nm-applet.eap
org.gnome.settings-daemon.plugins.sharing.service
org.mate.panel.toplevel
ca.desrt.dconf-editor.Lib
org.mate.panel.toplevel.background
org.gnome.Terminal.Legacy.Keybindings
ca.desrt.dconf-editor.Demo.EmptyRelocatable
org.gnome.desktop.notifications.application
org.gnome.desktop.app-folders.folder
Known schemas skipped:
org.gnome.settings-daemon.peripherals.wacom.stylus.deprecated
org.gnome.settings-daemon.peripherals.wacom.deprecated
org.gnome.settings-daemon.peripherals.touchpad.deprecated
ca.desrt.dconf-editor.Demo.Relocatable
org.gnome.settings-daemon.peripherals.keyboard.deprecated
org.gnome.settings-daemon.peripherals.wacom.tablet-button.deprecated
org.gnome.Terminal.SettingsList
org.gnome.settings-daemon.peripherals.wacom.eraser.deprecated
org.gnome.settings-daemon.peripherals.trackball.deprecated
org.gnome.settings-daemon.peripherals.mouse.deprecated
org.gnome.yelp.documents
Unknown schemas:
org.gnome.shotwell.printing
org.gnome.Patience.WindowState
org.mate.panel.applet.netspeed
org.freedesktop.pulseaudio.module-group
org.gnome.shotwell.sharing.org-gnome-shotwell-publishing-tumblr
org.gnome.settings-daemon.plugins.xsettings.deprecated
org.mate.panel.applet.geyes
org.gnome.desktop.peripherals.touchscreen
org.gnome.settings-daemon.plugins.media-keys.deprecated
org.gnome.seahorse.nautilus.window
org.gnome.Polari.Account
org.gnome.brasero.plugins
org.mate.control-center.keybinding
org.mate.panel.applet.cpufreq
org.a11y.Accerciser.hotkeys
org.gnome.shotwell.plugins.enable-state
org.blueman.gsmsetting
org.gnome.LightsOff.Lib
org.gnome.desktop.peripherals.tablet.deprecated
org.gnome.shotwell.dataimports
org.gnome.shotwell.sharing.org-gnome-shotwell-publishing-google-photos
org.mate.panel.applet.workspace-switcher
org.mate.panel.applet.notification-area
org.mate.panel.applet.timer
org.gnome.desktop.peripherals.tablet.pad-button
org.gnome.shotwell.sharing.flickr
org.gnome.shotwell.preferences.ui
org.gnome.shotwell.preferences.slideshow
org.mate.panel.applet.charpick
org.gnome.desktop.peripherals.tablet.stylus
org.mate.panel.applet.window-list-previews
org.mate.panel.applet.multiload
org.gnome.shotwell.preferences.editing
org.gnome.shotwell.preferences.window
org.gnome.brasero.drives
org.mate.terminal.profile
org.blueman.plugins.netusage
org.gnome.shotwell.sharing.org-gnome-shotwell-publishing-piwigo
org.mate.panel.applet.battstat
org.gnome.shotwell.sharing
org.gnome.shotwell.sharing.youtube
org.mate.panel.applet.command
org.gnome.shotwell.preferences.export
org.gnome.portal.filechooser
org.mate.panel.applet.clock
org.gnome.shotwell.preferences.files
org.gnome.desktop.peripherals.tablet
org.virt-manager.virt-manager.connection
org.mate.panel.applet.window-list
org.virt-manager.virt-manager.vm
org.a11y.Accerciser.newpluginviews
org.mate.panel.applet.fish
org.gnome.shotwell.sharing.publishing-gallery3
org.gnome.shotwell.crop-settings
org.mate.weather
org.gnome.evolution.window
(base) tom@mydesktop: ~ $
I am running on x11; with mate desktop.
dconf-editor did run fine on 15.5. Only new thing is switch to 15.6. I don’t remember using it after the switch-over so I was thinking there was a 15.6 issue but you disproved that.
Tried starting it from a desktop launcher and also from terminal. No difference seen.
gconf editor runs fine.
Hello again @tckosvic
The “–list-relocatable-schemas” was as much to test that the cli worked as anything else. I did not see anything odd in the output and I honestly did not expect that I would.
My meager test proved only that I am not having the same problem, whatever it may actually be …
I should have thought to write this last night before I went to sleep, but sleepy penguins don’t always think so well. You may gain some insight by examining the system messages, which can be done easily enough with the “journalctl” command.
For example:
root@orca# journalctl -b --no-host
Aug 01 10:38:25 kernel: microcode: updated early: 0x84 -> 0xf8, date = 2023-09-28
Aug 01 10:38:25 kernel: Linux version 6.4.0-150600.23.14-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.4>
Aug 01 10:38:25 kernel: Command line: BOOT_IMAGE=/vmlinuz-6.4.0-150600.23.14-default root=UUID=f9ad0342-a904-43d2-a6d2-e60fe1696d68 splash=silent preempt=full >
Aug 01 10:38:25 kernel: BIOS-provided physical RAM map:
... FOLLOWED BY TONS OF STUFF, SOME OF WHICH MIGHT BE INTERESTING! ...
Unfortunately (or fortunately for me), I don’t have any examples of an app dumping core in my system journals at the moment.
As a temporary work around, you should be able read and write dconf values from the cli.
Until I installed Leap 15.6, I strongly preferred to run gnome on X11. I switched to wayland only recently for the sole reason that Gnome + X11 + Nvidia G06 drivers does not work well in Leap 15.6. I do not KNOW that the Nvidia driver is required to cause the problems I encountered or not. I mention all this because dconf-editor is a gtk4 app and I am not convinced that gtk4 and its evil cousins still play nice with X11.
I would very much like to see what your system journal tells you immediately before and after dumping core. I suspect, while hoping to be wrong, that you will see some complaining from the display manager.
You can also use something like:
nohup strace dconf-editor > dconf_dump.txt 2>&1
if the system journal fails to reveal anything useful.
Happy Monday!
I got this from yast system log. Perhaps someone can see something. I did try rebooting into previous kernel and got same seg fault.
By the way, I have run leap15.6 → gnome → x11 → nvidia G06 with no issues. I mostly use mate but did run gnome and gnome classic seemingly ok.
2024-08-05T09:03:41.024878-05:00 mydesktop kernel: [ 1132.905974][ T7054] dconf-editor[7054]: segfault at 2f6e ip 00007f4ab7469c5e sp 00007ffc4ab215d0 error 4 in libglib-2.0.so.0.7800.6[7f4ab7425000+143000] likely on CPU 3 (core 3, socket 0)
2024-08-05T09:03:41.024896-05:00 mydesktop kernel: [ 1132.905992][ T7054] Code: 1f 44 00 00 48 8b 4c 24 20 48 85 c9 0f 84 8d 04 00 00 48 63 44 24 1c 48 89 c2 48 8b 04 c1 48 89 44 24 08 8d 42 01 89 44 24 1c <41> 80 3c 24 00 74 4b 8b 4c 24 2c 85 c9 0f 85 4f 01 00 00 4c 89 e7
2024-08-05T09:03:41.069576-05:00 mydesktop systemd[1]: Started Process Core Dump (PID 7065/UID 0).
2024-08-05T09:03:41.073001-05:00 mydesktop systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2024-08-05T09:03:41.358799-05:00 mydesktop systemd-coredump[7066]: Process 7054 (dconf-editor) of user 1000 dumped core.#012#012Stack trace of thread 7054:#012#0 0x00007f4ab7469c5e n/a (libglib-2.0.so.0 + 0x44c5e)#012#1 0x00007f4ab746b155 g_build_filename (libglib-2.0.so.0 + 0x46155)#012#2 0x00007f4ab76ca454 g_settings_schema_source_new_from_directory (libgio-2.0.so.0 + 0xf8454)#012#3 0x000055a7ef43d942 n/a (dconf-editor + 0x74942)#012#4 0x000055a7ef44110c source_manager_refresh_schema_source (dconf-editor + 0x7810c)#012#5 0x000055a7ef40a699 _settings_model_core_finalize_model (dconf-editor + 0x41699)#012#6 0x000055a7ef412680 dconf_window_construct (dconf-editor + 0x49680)#012#7 0x000055a7ef404ab9 n/a (dconf-editor + 0x3bab9)#012#8 0x000055a7ef404b6e n/a (dconf-editor + 0x3bb6e)#012#9 0x000055a7ef405ff9 n/a (dconf-editor + 0x3cff9)#012#10 0x00007f4ab765ac35 n/a (libgio-2.0.so.0 + 0x88c35)#012#11 0x00007f4ab758145c n/a (libgobject-2.0.so.0 + 0x1645c)#012#12 0x00007f4ab75980e2 n/a (libgobject-2.0.so.0 + 0x2d0e2)#012#13 0x00007f4ab75a0d11 g_signal_emit_valist (libgobject-2.0.so.0 + 0x35d11)#012#14 0x00007f4ab75a0dcf g_signal_emit (libgobject-2.0.so.0 + 0x35dcf)#012#15 0x00007f4ab76b4953 n/a (libgio-2.0.so.0 + 0xe2953)#012#16 0x00007f4ab76b6c72 n/a (libgio-2.0.so.0 + 0xe4c72)#012#17 0x00007f4ab76b6e16 g_application_run (libgio-2.0.so.0 + 0xe4e16)#012#18 0x000055a7ef3e803a main (dconf-editor + 0x1f03a)#012#19 0x00007f4ab6840eec __libc_start_call_main (libc.so.6 + 0x40eec)#012#20 0x00007f4ab6840fb5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x40fb5)#012#21 0x000055a7ef3e8091 _start (dconf-editor + 0x1f091)#012#012Stack trace of thread 7055:#012#0 0x00007f4ab692c709 syscall (libc.so.6 + 0x12c709)#012#1 0x00007f4ab74db4be g_cond_wait (libglib-2.0.so.0 + 0xb64be)#012#2 0x00007f4ab744d23b n/a (libglib-2.0.so.0 + 0x2823b)#012#3 0x00007f4ab74afa82 n/a (libglib-2.0.so.0 + 0x8aa82)#012#4 0x00007f4ab74af48e n/a (libglib-2.0.so.0 + 0x8a48e)#012#5 0x00007f4ab68a761c start_thread (libc.so.6 + 0xa761c)#012#6 0x00007f4ab692eaa8 __clone3 (libc.so.6 + 0x12eaa8)#012#012Stack trace of thread 7056:#012#0 0x00007f4ab692055f __poll (libc.so.6 + 0x12055f)#012#1 0x00007f4ab7481b61 n/a (libglib-2.0.so.0 + 0x5cb61)#012#2 0x00007f4ab74821cc g_main_context_iteration (libglib-2.0.so.0 + 0x5d1cc)#012#3 0x00007f4ab7482211 n/a (libglib-2.0.so.0 + 0x5d211)#012#4 0x00007f4ab74af48e n/a (libglib-2.0.so.0 + 0x8a48e)#012#5 0x00007f4ab68a761c start_thread (libc.so.6 + 0xa761c)#012#6 0x00007f4ab692eaa8 __clone3 (libc.so.6 + 0x12eaa8)#012#012Stack trace of thread 7057:#012#0 0x00007f4ab692055f __poll (libc.so.6 + 0x12055f)#012#1 0x00007f4ab7481b61 n/a (libglib-2.0.so.0 + 0x5cb61)#012#2 0x00007f4ab7482402 g_main_loop_run (libglib-2.0.so.0 + 0x5d402)#012#3 0x00007f4ab76f2ee6 n/a (libgio-2.0.so.0 + 0x120ee6)#012#4 0x00007f4ab74af48e n/a (libglib-2.0.so.0 + 0x8a48e)#012#5 0x00007f4ab68a761c start_thread (libc.so.6 + 0xa761c)#012#6 0x00007f4ab692eaa8 __clone3 (libc.so.6 + 0x12eaa8)#012#012Stack trace of thread 7058:#012#0 0x00007f4ab692055f __poll (libc.so.6 + 0x12055f)#012#1 0x00007f4ab7481b61 n/a (libglib-2.0.so.0 + 0x5cb61)#012#2 0x00007f4ab74821cc g_main_context_iteration (libglib-2.0.so.0 + 0x5d1cc)#012#3 0x00007f4ab501726d n/a (libdconfsettings.so + 0xb26d)#012#4 0x00007f4ab74af48e n/a (libglib-2.0.so.0 + 0x8a48e)#012#5 0x00007f4ab68a761c start_thread (libc.so.6 + 0xa761c)#012#6 0x00007f4ab692eaa8 __clone3 (libc.so.6 + 0x12eaa8)#012#012Stack trace of thread 7064:#012#0 0x00007f4ab692c709 syscall (libc.so.6 + 0x12c709)#012#1 0x00007f4ab74db655 g_cond_wait_until (libglib-2.0.so.0 + 0xb6655)#012#2 0x00007f4ab744d221 n/a (libglib-2.0.so.0 + 0x28221)#012#3 0x00007f4ab74afc76 n/a (libglib-2.0.so.0 + 0x8ac76)#012#4 0x00007f4ab74af48e n/a (libglib-2.0.so.0 + 0x8a48e)#012#5 0x00007f4ab68a761c start_thread (libc.so.6 + 0xa761c)#012#6 0x00007f4ab692eaa8 __clone3 (libc.so.6 + 0x12eaa8)#012ELF object binary architecture: AMD x86-64
2024-08-05T09:03:41.389889-05:00 mydesktop systemd[1]: systemd-coredump@5-7065-0.service: Deactivated successfully.
2024-08-05T09:03:41.783099-05:00 mydesktop drkonqi-coredump-processor[7067]: "/usr/bin/dconf-editor" 7054 "/var/lib/systemd/coredump/core.dconf-editor.1000.603499c1b2a146279d3f6f78a1dd32f3.7054.1722866621000000.zst"
2024-08-05T09:03:41.783227-05:00 mydesktop drkonqi-coredump-processor[7067]: The socket path doesn't exist @ "/run/user/1000/drkonqi-coredump-launcher"
2024-08-05T09:03:41.799153-05:00 mydesktop systemd[1]: drkonqi-coredump-processor@5-7065-0.service: Deactivated successfully.
2024-08-05T09:04:12.747036-05:00 mydesktop mate-power-mana[4780]: levels is 0!
2024-08-05T09:04:12.784250-05:00 mydesktop pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
2024-08-05T09:04:12.784942-05:00 mydesktop pkexec[7090]: tom: Executing command [USER=root] [TTY=unknown] [CWD=/home/tom] [COMMAND=/usr/sbin/mate-power-backlight-helper --set-brightness 0]
2024-08-05T09:04:12.786670-05:00 mydesktop /usr/lib/gdm/gdm-x-session[7090]: No backlights were found on your system
2024-08-05T09:05:09.046662-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:05:09.047049-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:05:09.047153-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:05:09.047246-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:05:09.047337-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:05:09.047426-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:05:09.047513-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:05:09.047599-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:06:38.384589-05:00 mydesktop mate-power-mana[4780]: levels is 0!
2024-08-05T09:06:38.419274-05:00 mydesktop pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
2024-08-05T09:06:38.419982-05:00 mydesktop pkexec[7143]: tom: Executing command [USER=root] [TTY=unknown] [CWD=/home/tom] [COMMAND=/usr/sbin/mate-power-backlight-helper --set-brightness 0]
2024-08-05T09:06:38.421633-05:00 mydesktop /usr/lib/gdm/gdm-x-session[7143]: No backlights were found on your system
2024-08-05T09:06:46.089440-05:00 mydesktop boinc[2413]: 05-Aug-2024 09:06:46 [Asteroids@home] Sending scheduler request: To report completed tasks.
2024-08-05T09:06:46.089615-05:00 mydesktop boinc[2413]: 05-Aug-2024 09:06:46 [Asteroids@home] Reporting 9 completed tasks
2024-08-05T09:06:46.089685-05:00 mydesktop boinc[2413]: 05-Aug-2024 09:06:46 [Asteroids@home] Not requesting tasks: don't need (not highest priority project)
2024-08-05T09:06:48.091892-05:00 mydesktop boinc[2413]: 05-Aug-2024 09:06:48 [Asteroids@home] Scheduler request completed
2024-08-05T09:06:48.092089-05:00 mydesktop boinc[2413]: 05-Aug-2024 09:06:48 [Asteroids@home] Project requested delay of 7 seconds
2024-08-05T09:10:09.045161-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:10:09.066898-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:10:09.066997-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:10:09.067084-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:10:09.067158-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:10:09.067231-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:10:09.067299-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:10:09.067365-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:12:30.202890-05:00 mydesktop wnck-applet[4666]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
2024-08-05T09:12:35.825638-05:00 mydesktop wnck-applet[4666]: message repeated 25 times: [ Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)]
2024-08-05T09:15:09.047596-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:15:09.097783-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:15:09.097878-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:15:09.097954-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:15:09.098036-05:00 mydesktop caja[4655]: GFileInfo created without standard::sort-order
2024-08-05T09:15:09.098106-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached
2024-08-05T09:15:09.098173-05:00 mydesktop caja[4655]: GFileInfo created without standard::symlink-target
2024-08-05T09:15:09.098241-05:00 mydesktop caja[4655]: file ../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached
2024-08-05T09:15:10.764989-05:00 mydesktop wnck-applet[4666]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
2024-08-05T09:15:15.012458-05:00 mydesktop wnck-applet[4666]: message repeated 17 times: [ Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)]
2024-08-05T09:15:18.161495-05:00 mydesktop org.opensuse.YaST.desktop[6591]: Run command: /usr/bin/nohup /usr/sbin/yast2 view_anymsg '/var/log/messages' > /var/log/YaST2/nohup.out 2>&1 &
2024-08-05T09:15:18.874814-05:00 mydesktop wnck-applet[4666]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
Hello again @tckosvic
The keyword is “seemingly”! I used gnome+x11+g06 for a week to ten days before I really started noticing the problems, which become much more apparent under high load.
Back to the real issue at hand!
Unfortunately, there is nothing obviously helpful in the journal, at least not to my eyes.
The good news is that you have a coredump file to analyze: “/var/lib/systemd/coredump/core.dconf-editor.1000.603499c1b2a146279d3f6f78a1dd32f3.7054.1722866621000000.zst”
I have limited experience with analyzing coredumps, but there seem to be some good tools, perhaps already on your box, that appear to make it a little easier. Google really does help me push the boundaries of my knowledge 
.
As of now, it is looking like a bug in dconf-editor itself, but I don’t have much confidence in that assessment. Hopefully, someone with more knowledge than myself will join the thread.
Later today, I should have time to try and reproduce the problem here … just need complete a few tasks and install mate …
Until then!
Hello,
I installed mate and was unable to reproduce the problem. gconf-editor worked as expected.
I am genuinely at a complete loss as to what might be causing it to dump core on you setup.
@ oxwrongagain, just to confirm that my problem is with dconf-editor throwing segfault. Did you try running that? My installed gconf-editor runs fine and works as expected.
thanks for your time in looking into my issue.
tom kosvic
Hello @tckosvic ,
YES! I explicitly tested dconf-editor. I think it is the first time I have ever run a program and been disappointed not to get a core dump 
.
While I was at it, I also tested a few other things that have been bothering me. There is definitely some weirdness going on around gnome, nvidia, and x11.
The plot thickens. I logged out from mate desktop into gnome-classic-x11 desktop and dconf-editor worked fine. I did not try the other gnome variations.
Looks like a mate desktop thing. dconf commandline works fine on mate but dconf-editor does not. Looks like cause of segfault is related to graphical apps on mate. I have been using mate for 10 years or so. dconf-editor did work fine on mate until recently. I see nothing abnormal about other mate graphical apps.
What are the graphical processes that dconf-editor uses in mate that would be different from gnome? mate and gnome are related.
thanks, tom kosvic
Hello again @tckosvic ,
The plot thickens indeed!
Since dconf-editor worked for me on mate, I am going to take a wild guess that there is something wrong lurking somewhere within the .config directory, or perhaps elsewhere.
You can test my hunch easily enough. Create a new user. Log into mate as that new user and see if dconf-editor works.
If the fresh user works, I would suspect something along the lines of:
./.config/gtk-2.0
./.config/gtk-2.0/gtkfilechooser.ini
./.config/gtk-4.0
./.config/gtk-3.0
But I genuinely do not know.
Happy hunting!
You’re right on target so far. A new user, running mate, successfully ran dconf-editor.
Interesting that new user with the working dconf-editor had only .config/gtk-3.0 in its home directory. No refs to gtk-2 or gtk-4.
I think this narrows it down to a problem within .config/gtk-3.0 for my standard user.
I wonder if I just delete the gtk-3.0 directory(or rename it temporarily) if new correct files would be automatically generated into a new gtk-3.0 upon a reboot?
Just rename it … and no need to reboot (that’s for Windows users), simply log out and log back in.
You might also check in the ~/.cache subdir first … many browser issues are resolved by deleting their respective .cache subdirs.
I did rename gtk-3.0 directory and did reboot. But dconf-editor still threw a segfault. A new gtk-3.0 was created with only a user file in it.
Will look into ~/.cache and see what looks related to dconf-editor.
Hello @tckosvic ,
In .cache, I would look for anything graphics releated, such as “.cache/mesa_shader_cache”.
Another possible culprit is “.xintitrc”.
Cheers
Technically, and believe it or not, you can simply delete everything under the ~/.cache subdirectory… (keep the .cache subdir there)
It is simply that - it’s only a cache so responses in most used applications happen faster.
It’s the same as is used by many browsers … browsers use a cache to enhance response time for frequently accessed websites. But you can “clean” the browser’s cache (delete) and it won’t affect its use.
I deleted all directories and files in /.cache. dconf-editor still throws segfault.
Freed a lot of disk space but did not solve my problem.
thanks for the idea. tom kosvic
Dconf-editor now loads in mate. I needed to deactivatre “anaconda python”, i.e., exit the base environment. The anaconda commands put into .bashrc were altering the path so that the system was looking for libconf1 (a dependency of dconf-editor) inside a wrong directory in my home instead of the system libconf1 needed to run dconf-editor.
Who would have thunk that? Without “strace” string provided by @aggie in another thread I started, I would have never had the information to even get close to properly diagnosing the issue.
tom kosvic