Why does ghostty fail to start on Artix Linux?
Sent message to Artix forum, list the error, asking if ghostty needed systemd.
Error starting ghostty by a system folder file link: Failed to execute program com.mitchellh.ghostty: No such file or directory running ghostty inside konsole (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) …. info(io_exec): found Ghostty resources dir: /usr/share/ghostty info(io_exec): shell integration automatically injected shell=.bash info(opengl): loaded OpenGL 4.6 error(gtk_systemd_cgroup): creating transient cgroup scope failed code=2 err=GDBus.Error:org.freedeskt op.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files warning(gtk_post_fork): unable to create transient systemd scope app-ghostty-surface-transient-21734.s cope: DbusCallFailed
I couldn't find Mitchellh anywhere. What is happening here? Please help.
com.mitchellh.ghostty is not the name of an executable. It is Ghostty’s application ID, derived from Mitchell Hashimoto’s name. The actual executable is normally simply:
ghostty
The repository uses that ID in several places—for example, the desktop file uses it as the icon and application ID, while Exec= is supposed to contain the actual Ghostty executable path:
TryExec=@GHOSTTY@
Exec=@GHOSTTY@ --gtk-single-instance=true
Icon=com.mitchellh.ghostty
DBusActivatable=true
Therefore, if your launcher says:
Failed to execute program com.mitchellh.ghostty: No such file or directory
then the installed or manually-created desktop entry is probably incorrectly trying to execute the application ID. Check it with:
grep -E '^(Name|TryExec|Exec|Icon|DBusActivatable)=' \
/usr/share/applications/com.mitchellh.ghostty.desktop
command -v ghostty
Exec= and TryExec= should point to ghostty or, preferably, an absolute path such as:
TryExec=/usr/bin/ghostty
Exec=/usr/bin/ghostty --gtk-single-instance=true
Icon=com.mitchellh.ghostty is correct; it is only the icon/application identifier and must not be used as Exec=.
There is also a separate issue in your log:
error(gtk_systemd_cgroup): creating transient cgroup scope failed
...
The name org.freedesktop.systemd1 was not provided
Ghostty’s Linux default is:
linux-cgroup = single-instance
The source documents that this feature requires systemd. Ghostty attempts to create a transient systemd scope for each terminal surface by calling:
org.freedesktop.systemd1.Manager.StartTransientUnit
On Artix, where systemd is not normally running, that call fails. However, the default is non-fatal:
linux-cgroup-hard-fail = false
That is why Ghostty continues to run when started from Konsole. The warning means that cgroup resource isolation is unavailable; it does not mean that Ghostty generally requires systemd.
You can suppress the warning by adding this to your Ghostty configuration:
linux-cgroup = never
The gtk_systemd_cgroup code confirms that linux-cgroup = never returns without attempting the systemd D-Bus call.
There may be another Artix-specific launcher problem: the generated non-Flatpak D-Bus service contains:
[D-BUS Service]
Name=@APPID@
SystemdService=app-@APPID@.service
Exec=@GHOSTTY@ --gtk-single-instance=true --initial-window=false
The repository intentionally installs this systemd user-service integration for normal Linux installations. On a non-systemd system, D-Bus activation may therefore fail even though directly running ghostty works.
As a workaround, try changing the desktop entry to:
DBusActivatable=false
and ensure its Exec= line points to the real executable. Alternatively launch it directly with:
ghostty
For an Artix package, the proper packaging fix would likely be to either:
- disable/remove the
SystemdService=D-Bus activation integration for non-systemd installations, or - install a desktop entry configured to use ordinary
Exec=activation.
In short:
com.mitchellh.ghosttyis an application ID, not a missing program.- The
systemd1warning is expected on Artix and only disables optional cgroup isolation. - Set
linux-cgroup = neverto remove that warning. - Check the desktop file’s
Exec=andTryExec=entries; they must refer toghostty, notcom.mitchellh.ghostty. - If the launcher uses D-Bus activation, try
DBusActivatable=falseor ask the Artix package maintainer to adjust the desktop/D-Bus files for non-systemd systems.
END OF POST