From 8ad04e2eb43530b6aa1d99fdc9c53b378392155d Mon Sep 17 00:00:00 2001
From: Hyperling <me@hyperling.com>
Date: Sat, 19 Sep 2026 09:18:28 -0700
Subject: [PATCH] Add article on Artix dconf issues.

---
 .../tech/20260919-artix-dconf-issues.md       | 91 +++++++++++++++++++
 1 file changed, 91 insertions(+)
 create mode 100644 content/posts/guides/tech/20260919-artix-dconf-issues.md

diff --git a/content/posts/guides/tech/20260919-artix-dconf-issues.md b/content/posts/guides/tech/20260919-artix-dconf-issues.md
new file mode 100644
index 0000000..7521631
--- /dev/null
+++ b/content/posts/guides/tech/20260919-artix-dconf-issues.md
@@ -0,0 +1,91 @@
+---
+draft: false
+pinned: false
+hidden: false
+title: "Artix w/ runit and i3"
+subtitle: "Resolving Critical DConf Issues"
+feathericon: "cpu"
+author: Hyperling
+date:    2026-09-11T08:00:00-07:00
+#started:    2026-07-15T14:59:10-07:00
+lastmod: 2026-09-11T13:00:00-07:00
+toc: true
+audio: false
+images:
+tags:
+  - tech # food, drink, craft, poetry, blog, video, tech, tourism
+  - linux
+  - arch
+  - artix
+  - runit
+  - systemd
+  - dconf
+  - lightdm
+  - sddm
+  - elogind
+  - logind
+series:
+  - sysadmin
+categories:
+  - guides # recipes, musings, videos, articles
+  - articles
+aliases:
+  - /posts/guides/tech/20260919-artix-dconf-issues
+  - /posts/guides/tech/artix-dconf-issues
+  - /artix-dconf-issues
+---
+
+## Introduction
+
+Sometimes when logging in to my Artix installation I'd get an array of `dconf` errors from multiple programs.
+i3's status bar would not show up, certain programs like Codium would not launch,
+ and the system would just behave in peculiar ways.
+
+```console
+dconf-CRITICAL **: 07:54:25.230: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.
+```
+
+Checking `logind` would show that it was running, and `loginctl list-sessions` would list the session, but the `/run/user` directory would be completely empty.
+Any attempt to manually create the hierarchy would cause the new folders to get immediately and completely nuked.
+Restarting and enabling `logind` did not seem to have any effect.
+
+On my other system I had been using `lightdm` without issues,
+ and on this one I had been using `sddm` since it was allowing login back before [resolving the graphical issues](/artix-intel-gpu).
+I switched back to `lightdm` and it ended up alleviating this situation.
+It's a super simple process that I've detailed below.
+
+## Instructions
+
+This one is easy. All you need to do is switch from `sddm` (or whatever) to `lightdm`.
+
+First ensure all the packages are installed.
+If it asks you to remove any conflicting packages (such as `sddm-runit`), choose Y.
+
+```console
+$ sudo pacman -Sy lightdm lightdm-runit
+```
+
+Next ensure the service script is linked.
+
+```console
+$ sudo ln -s /etc/runit/sv/lightdm /run/runit/service/
+```
+
+Then reboot, choose your display manager at the login screen, and enjoy!
+
+## Cleanup
+
+If you'd like, you can also now remove the old display manager from your services.
+
+```console
+$ sudo rm -v /run/runit/service/sddm
+```
+
+Since the script (`sddm-runit` in this case) has been uninstalled it doesn't really matter,
+ but it can help prevent confusion down the road if you forget which you're actually using.
+
+Happy hacking! :)
+
+---
+
+[blog.hyperling.com/artix-intel-gpu](/artix-intel-gpu)