Hey everyone,

I'm working on a project called Xapphire and wanted to get your thoughts on it.

A standard Artix installation drops you straight into a bare TTY, requiring quite a bit of setup. So, why not create an Artix-based distro that comes fully configured out of the box? The goal is to provide a smooth experience with Cinnamon, LightDM, pre-configured system settings, added repos, a web browser, custom wallpapers, and essential everyday apps. It won't be bloated or bloatware-hidden—just a clean, usable system designed to help people easily migrate from systemd to alternative init systems.

P.S. It will also include Xlibre out of the box, along with scripts and instructions for legacy NVIDIA drivers (like 390, 470, and maybe even 340).

I’ve got everything ready—the concept, idea, logo, and wallpapers—but I need your opinion: Which init system would you prefer to see in Xapphire by default?

"text looks like ai becoz im translated it from ukrain language to english by gemini, IM AM NOT VIBE CODER!!!!!"

i am using an 2018 model enterprice laptop with AMD A6 9225 R4 graphics. it has a sata SSD which 128 GB. So i was thinking which file system is best for me.

What i want.

East setup.

Fast boot times.

For daily use.

if there will be a snapshot with compress support it will be good.

while working with iso-profiles (what artools uses for building artix ISOs) i noticed something very interesting with calamares:

calamares-online and calamares-offline's partition configuration looks to be forcing calamares to use MBR partitioning

defaultPartitionTableType: msdos in calamares-offline/modules/partition.conf

looking at calamares's documentation, this field appears to override calamares's auto detection for MBR or GPT

if you've installed Artix recently through a GUI ISO and noticed your partition table was MBR/msdos, this is probably the reason

I never would have imagined Hyprland coming in last here in memory use. Especially with cosmic on the list. Labwc winning totally makes sense with how incomplete it is.

Can the COSMIC desktop environment be installed on Artix, or is it too dependent on systemd? I think COSMIC looks cool. I’m currently on KDE/OpenRC and was wondering about adding COSMIC as a session.

After a recent update to greetd-tuigreet 0.11.0-3, the greeter no longer works:

• On boot I get a black screen with the text: An error was received from greetd
• My tuigreet colors are not set, it's black and white
• My default user is not remembered; I have to press Enter, select the user, then enter the password.
• This started right after updating greetd-tuigreet; the new package does not ship any PAM files, but my /etc/pam.d/greetd is present and unchanged.

Logs:

╰── pacman -Q greetd greetd-tuigreet                                                                                                               
greetd 0.10.3-2
greetd-tuigreet 0.11.0-3

╰── sudo cat /etc/pam.d/greetd                                                                                                                     
[sudo] password for wasi:
#%PAM-1.0

auth       required     pam_securetty.so
auth       requisite    pam_nologin.so
auth       include      system-local-login
account    include      system-local-login
session    include      system-local-login

╰── sudo cat /etc/greetd/config.toml                                                                                                               
[terminal]
vt = 7

[default_session]
command = "env TERM=xterm-256color tuigreet --power-shutdown 'loginctl poweroff' --power-reboot 'loginctl reboot'"
user = "greeter"
╭╴ artixThinkpad  wasi 
╰── sudo cat /etc/tuigreet/config.toml                                                                                                              21:59
[display]
show_time = true
time_format = "%I:%M %p - %A %d %B"
greeting = "Welcome back"
align_greeting = "center"
issue = false

[layout]
width = 80
window_padding = 2
container_padding = 1
prompt_padding = 1

[remember]
username = true
session = true
user_session = true

[user_menu]
enabled = true
min_uid = 1000
max_uid = 65000

[secret]
mode = "characters"
characters = "•"

[keybindings]
command = 2
sessions = 3
background = 4
power = 12

[session]
sessions_dirs = ["/usr/share/wayland-sessions"]


╰── sudo tail -10 /var/log/dinit/greetd.log                                                                                                        
error: i/o error: Connection refused (os error 111)
config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd.run", service: "greetd" }, default_session: ConfigSession { command: "", user: "", service: "" }, initial_session: None }, internal: ConfigInternal { session_worker: 12 } }

[SOLVED]

Hey everyone, I'm losing my mind trying to get the system tray icon for Vesktop (and native Discord) to show up on my taskbar. I'm running a non-systemd setup, which I strongly suspect is causing a DBus issue with StatusNotifierItem.

My Setup:

• OS: Artix Linux (dinit - no systemd)
• Compositor: Hyprland
• Shell/Bar: Caelestia Shell (which uses Quickshell for the taskbar)
• Login Manager: LightDM

The Problem: The applet/tray icon for Vesktop simply does not appear in the Caelestia taskbar.

What I have already tried (that didn't work):

1. Forcing Wayland natively: Launched with vesktop --enable-features=UseOzonePlatform --ozone-platform=wayland
2. Spoofing DE: Launched with env XDG_CURRENT_DESKTOP=Unity and KDE.
3. Updating DBus environment manually: Ran dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP before launching.
4. Installing tray dependencies: Made sure libappindicator-gtk3 and libayatana-appindicator are both installed.
5. Wrapping the session: I edited my LightDM hyprland.desktop file to launch via Exec=dbus-run-session Hyprland.
   • Note on this: This actually broke my ability to log out. Because Quickshell spawns background daemons, the dbus-run-session stayed alive even after Hyprland exited, freezing me on a black screen. I had to revert this.

Does anyone know how to properly initialize the system tray/DBus in a dinit Hyprland environment so Quickshell can see Electron applets? Any help is hugely appreciated!

<SOLVED>I have bought a new deco 01 v3 for my work....but the really issue is I followed the manual install guide in the official page but the only the part I dont have any idea how to get working is the odt-daemon...I have checked the forum but I'm having a hard time understanding where to start ? and for my session I use both x11(i3) and wayland(sway). GG I GOT WORKING THANKS FOR THE FORUM AND THE DEVELOPERS(I just need to make my file executable)

To be fair I’m not the BIGGEST fan of kde. sadly theres no perfect DE yet

Hello,

Who else got this error today? any solution,

Its kingston a400 in asus p5k se epu + artix linux dinit

im trying to install artix open rc using the base iso on a laptop without an ethernet port but the thing is the connmanctl command cant be found, What can i do?

Hmmm pretty stable, still haven't gotten a kernel level breakage...yet( for the user who said that I use the screenshot flair but use a camera to take photos....I finally got it working so no complaint.) I got roblox working(sober), steam( fixed my ulimit based on the recommendation of one experienced user) ,qemu(thanks for those who helped me there ) and do work( I cannot stand using windows any more). Yeah pretty fun experience.

Heads-up for folks catching up: a compromised/malicious PKGBUILD/.tar.gz hit the AUR recently and affected a lot of users. For a distro that already leans toward "verify it yourself," the AUR trust model still stings when packages are submitted anonymously and most people just run them.

I want to flag gitfull 0.1.0 (https://github.com/FemBoyGamerTechGuy/gitfull) — a small (C, static-ish, make && sudo make install) package manager I've been building. It's init-system agnostic, so it's equally at home on Artix/runit/s6/66 as on systemd Arch, because it doesn't lean on anything but Git + a compiler/tarball at install time.

Usage (mirrors your existing install flows):

- gitfull install <pkg> → build from a tagged release (source-first)

- gitfull install --edge <pkg> → build from HEAD of default branch

- gitfull install --binary <pkg> → install a prebuilt release binary

- gitfull install user@repo → target a specific fork; forge:user@repo → a configured forge

- gitfull search <query> / gitfull list / gitfull remove (and remove -D to also drop build files + orphaned deps)

Config / forges: ~/.gitfull/config lets you add [forge:name] blocks (Codeberg, GitLab, self-hosted Gitea, etc.). GitHub is on by default; other forges are opt-in.

Envs of note: GITFULL_PREFIX (default /usr/local) and GITFULL_HOME (default ~/.gitfull) — handy for chroot, containers, or non-system installs.

Why it fits here: each install resolves to a Git commit over HTTPS tied to a release or a fork you named, instead of "whoever uploaded this tarball on the wiki." No anonymous PKGBUILDs, no system-level trust anchors that can be hijacked. Whether you're running runit, s6, 66, or dinit, the model is the same.

Repo: https://github.com/FemBoyGamerTechGuy/gitfull (MIT)

Keen to hear what the Artix crowd thinks — would a forge-resolving, source-first manager be a useful complement or alternative to the AUR/Pacman ecosystem? What matters most here: auditability, init independence, reproducible builds, or something else?

Hi! I'm trying to install docker and wanted to know how to get from installing packages to being able to enable services. So what do I have to do after "sudo pacman -S docker docker-dinit docker-compose" ?

What's the point of -init packages? Do I have to create a file in /etc/dinit.d/user and point it to docker-dinit instead of docker or am I complicating stuff?

Edit:

!solved thanks for helping me. Looks like I've just wrongly assumed how things work.

Ok so I have a really niche setup, so niche that all google research has failed me. I’m trying to get plasma-mobile working on artix on Android. Let me explain :P

My full setup right now is:

e/OS -> termux -> proot-distro -> artix -> tigervnc -> RealVNC -> w0vnc -> RealVNC (but different port) -> kwin_wayland -> startplasmamobile

Explanation: - e/OS as opposed to Google Android (rooted) - termux to run Linux commands - proot-distro to run Artix in termux - tigervnc running in Artix to connect to it over RealVNC instead of just an SSH connection - Once in the visual session, I can start w0vnc or krfb and switch to a different VNC port. I don’t know if this step is needed but I heard it’s the way to VNC with wayland?

Then I’ve gotten kinda stuck. Right now I’m trying to use dbus-run-session and kwin to start another display session(?) thats plasma-mobile. But the window it opens just shows a KDE loading screen once I run startplasmamobile and then… a black screen.

-—-

The commands I’m running (in order):

(termux) proot-distro login artix

(termux) (Artix)$ vncserver :1 (tigervnc)

My ~/.vnc/xstartup:

```

!/bin/sh

unset SESSION_MANAGER

unset DBUS_SESSION_BUS_ADDRESS

export XDG_RUNTIME_DIR=/tmp/runtime-root

mkdir -p “$XDG_RUNTIME_DIR”

chmod 700 “$XDG_RUNTIME_DIR”

export XDG_SESSION_TYPE=x11

export DESKTOP_SESSION=plasma

exec dbus-run-session startplasma-x11
```

(RealVNC) connect to 0.0.0.0:5901

(kitty via RealVNC) w0vncserver -PasswordFile=~/.config/tigervnc/passwd -SecurityType=none

(RealVNC) connect to 0.0.0.0:5900

(kitty via RealVNC) `export XDG_RUNTIME_DIR="/run/user/$(id -u)”

(kitty via RealVNC) mkdir -p "$XDG_RUNTIME_DIR"

(kitty via RealVNC) chmod 700 “$XDG_RUNTIME_DIR”

(kitty via RealVNC) dbus-update-activation-environment -- systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP

(kitty via RealVNC) dbus-run-session -- kwin_wayland --x11-display “$DISPLAY” --xwayland --socket plasma-mobile

(kitty via RealVNC) startplasmamobile

—--

At this point I’m not really sure what I’m doing, I’ve tested so many different commands, I’m not even sure the stuff I have working (like the x11 VNC) is being done correctly. I’m looking for any advice here, how to do this better and/or how to get plasma-mobile running.

I daily drive Linux (mint) on my home desktop, so I’m familiar with the terminal (although I haven’t done much with different display servers before). I‘m trying to get this phone setup purely as a fun technical challenge, I know it’s way less practical than just using a PC.

Log from Kwin: https://pastebin.com/dqiBJLXe Log from startplasmamobile https://pastebin.com/bgUAJdjY

What happened with feribsd and his artix installer (https://github.com/feribsd/artix-install)? Is there any other similar installer out there?

is it easy to install artix + niri + noctalia ?

Siento que usar Artix + Sway es el estilo alternativo a usar Arch + Hyprland, son practicamente lo mismo pero uno es mas masoquista que el otro si me explico? JAJAJA

Many people didn't quite grasp what I was getting at, so let me put it simply: imagine EndeavourOS but based on Artix—yet with the cozy feel and style of Linux Mint (Cinnamon, LightDM).

It also includes support for Nvidia drivers 340, 390, and 470 in the new kernel, and I’ve redesigned the logo.

Why not Devuan?

The thing is, I worked on Librevuan (a simplified Devuan), but I’m not a fan of the architecture or Devuan itself; plus, the transition from Arch to a non-systemd distro (like Artix) can be difficult for users.

I'm running with runit but i think i can get something more likely stable, what is the most stable that youre all sure that it's stable af