I don’t remember if it was always like this after I upgraded to Crimson, but I noticed I wasn’t receiving texts (SMS or matrix), so I started Chatty from the UI and I got a bunch of notifications. I then restarted my phone and ran ‘ps aux | grep -i chat’ from a terminal and saw no ‘chatty –daemon’ process.
Anyone else seeing this?
What’s the output of systemctl --user status sm.puri.Chatty-daemon.service?
× sm.puri.Chatty-daemon.service - SMS/MMS, Matrix and XMPP chat application (daemon mode)
Loaded: loaded (/usr/lib/systemd/user/sm.puri.Chatty-daemon.service; enabled; preset: enabled)
Active: failed (Result: signal) since Sun 2026-01-04 19:43:43 EST; 12h ago
Duration: 531ms
Process: 2272 ExecStart=/usr/bin/chatty --gapplication-service (code=killed, signal=TRAP)
Main PID: 2272 (code=killed, signal=TRAP)
CPU: 816ms
Jan 04 19:43:43 pureos systemd[866]: sm.puri.Chatty-daemon.service: Scheduled restart job, restart counter is at 10.
Jan 04 19:43:43 pureos systemd[866]: Stopped sm.puri.Chatty-daemon.service - SMS/MMS, Matrix and XMPP chat application (daemon mode).
Jan 04 19:43:43 pureos systemd[866]: sm.puri.Chatty-daemon.service: Start request repeated too quickly.
Jan 04 19:43:43 pureos systemd[866]: sm.puri.Chatty-daemon.service: Failed with result ‘signal’.
Jan 04 19:43:43 pureos systemd[866]: Failed to start sm.puri.Chatty-daemon.service - SMS/MMS, Matrix and XMPP chat application (daemon mode).
You’ll have to investigate why it was repeatedly failing to launch at Jan 04 19:43:43, as systemd only gave up after 10 failed attempts to launch it.
Just a hunch, but do you have Matrix account(s) connected?
This was bug/crash-prone for me on the Chatty version currently in Crimson, but works on newer Chatty versions much better.
Tried removing matrix accounts first. FWIW, compiled and installed pkg-chatty pureos/crimson branch, and now autostart is working. I wondered if it was due to my compiling chatty before with an upstream avatar-caused loop fix. Seems like it was the case.