Does ghostty need systemd to run outside konsole?
Hi My system is Artix-OpenRC-Plasma-SonicDE I installed ghostty from the galaxy. It won't run on its own. It will run in konsole. I'm trying to start ghostty outside konsole. Does ghostty need systemd?
Error starting ghostty by a system folder file link (partial list): Failed to execute program com.mitchellh.ghostty: No such file or directory [I got no help from his website]
running ghostty inside konsole (it runs but throws up this partial list):
info: reading configuration file path=/home/dh/.config/ghostty/config.ghostty
info(config): default shell src=passwd value=/bin/bash
info(config): default working directory src=passwd value=/home/dh
warning(gtk_ghostty_application): setting GDK_DEBUG=
warning(gtk_ghostty_application): setting GDK_DISABLE=vulkan
info(gtk_ghostty_surface): surface content scale: x=1 y=1 dpi=96x96 font_size=12
info(opengl): EGL vendor=Mesa Project
info(opengl): EGL extensions=E (a lot, edited for brevity)
Thanks for any help! :)
Hi! Ghostty does not require systemd to run on Artix/OpenRC. Your output shows that Ghostty starts correctly; the systemd message is about an optional feature:
creating transient cgroup scope failed
The name org.freedesktop.systemd1 was not provided
Ghostty uses systemd cgroups for per-window resource management. In the source, this is enabled by default on Linux in single-instance mode, but the failure is normally non-fatal (src/config/Config.zig).
##1. Disable the systemd cgroup feature
Add this line to:
~/.config/ghostty/config.ghostty
linux-cgroup = never
Then restart Ghostty. This should remove the warning. You can also use:
ghostty +show-config --default | grep linux-cgroup
The related source code explicitly documents never as the option for disabling cgroups and says that systemd is required only for this feature.
##2. The desktop launcher is a separate issue
The official Linux desktop file contains:
DBusActivatable=true
and the D-Bus service contains:
SystemdService=app-com.mitchellh.ghostty.service
That activation method assumes systemd. On Artix, KDE may therefore try to start Ghostty through D-Bus/systemd instead of directly executing the program. This likely explains:
Failed to execute program com.mitchellh.ghostty: No such file or directory
com.mitchellh.ghostty is Ghostty's application ID, not the executable name.
First check the actual executable path:
command -v ghostty
It will probably be:
/usr/bin/ghostty
Create a local desktop-file override:
mkdir -p ~/.local/share/applications
cp /usr/share/applications/com.mitchellh.ghostty.desktop \
~/.local/share/applications/com.mitchellh.ghostty.desktop
Edit the copied file:
nano ~/.local/share/applications/com.mitchellh.ghostty.desktop
Change:
DBusActivatable=true
to:
DBusActivatable=false
Also make sure these entries use the real executable path:
TryExec=/usr/bin/ghostty
Exec=/usr/bin/ghostty --gtk-single-instance=true
You may also change the action entry:
[Desktop Action new-window]
Name=New Window
Exec=/usr/bin/ghostty --gtk-single-instance=true
Afterward, log out and back in, or refresh KDE's application cache:
kbuildsycoca6
You can test the launcher directly with:
gtk-launch com.mitchellh.ghostty
Alternatively, bypass the desktop file and create a simple launcher containing only:
[Desktop Entry]
Type=Application
Name=Ghostty
Exec=/usr/bin/ghostty
TryExec=/usr/bin/ghostty
Icon=com.mitchellh.ghostty
Terminal=false
DBusActivatable=false
Categories=System;TerminalEmulator;
So, in summary:
- No, systemd is not required for normal Ghostty use.
- Set
linux-cgroup = neverto disable the optional systemd integration. - Set
DBusActivatable=falsein a local desktop entry so KDE executes/usr/bin/ghosttydirectly instead of attempting systemd/D-Bus activation.
END OF POST