Trilium Notes switched to the maintanence mode since Jan, 2024

Discuss
1

Hi, as some of you might know, the original Trilium project switched to the maintanence mode since Jan, 2024. See Announcement: Trilium transitions into maintenance mode · Issue #4620 · zadam/trilium · GitHub where the developer announced the situation.

I’ve found this reddit post when I was navigating on reddit. The post was an announcement about a new successor of the original Trilium and it is actively being developed on this github repo. As per it stated in their readme; TriliumNext is compatible with TriliumNotes makes it easy to migrate.

Disclaimer: I haven’t experimented with the successor project.

I was wondering what Yunohost app package maintainers would think on switching to the successor project?

1 Like
2

You can try GitHub - YunoHost-Apps/trilium_ynh at next-v2 and give feedback.
Make a backup before you proceed

1 Like
3

Oh :smiley:, there is already a Work In Progress then! That is nice to see. Of course, I will give it a try soon.

4

@jarod5001 I’ve installed it. When I navigate to it I’ve got 502 error. The service fails to start. Here is the reason:

5

I have just added a dependency to libnss3. Can you try upgrading again?

1 Like
6

Hi @tituspijean, I’ve reinstalled it. And this time, libatk-1.0.so.0 is missing:

Apr 24 11:30:55 systemd[1]: Started trilium.service - Trilium: notes server.
Apr 24 11:30:56 trilium[1529871]: /var/www/trilium/trilium: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory
Apr 24 11:30:56 systemd[1]: trilium.service: Main process exited, code=exited, status=127/n/a
Apr 24 11:30:56 systemd[1]: trilium.service: Failed with result 'exit-code'.
Apr 24 11:30:56 systemd[1]: trilium.service: Scheduled restart job, restart counter is at 1.
Apr 24 11:30:56 systemd[1]: Stopped trilium.service - Trilium: notes server.

By the way, how can I upgrade the already installed instance, instead of removing and installing it again?

7

Hi,

I’ve been retrying installing from the next-v2 branch. I installed the following libs that required by the trilium, manually with apt:

  • libatk1.0-0
  • libatk-bridge2.0-0
  • libgtk-3-0

This is how they are named in apt repo. Then I’ve started again the failed service. Then I got the following error:

trilium[2942622]: [2942622:0710/123113.622083:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /var/www/trilium/chrome-sandbox is owned by root and has mode 4755.
Jul 10 12:31:13 systemd[1]: trilium.service: Main process exited, code=killed, status=5/TRAP

I’ve changed the owner from trilium:trilium to root:trilium and permission from 4750 to 4755. But I kept getting the same error. I also tried changing the owner from root:trilium to root:root with no avail. Trilium keeps crashing. What would be the remedy for this?

Here is the latest log:

Edit

Ooops.. this error looks an upstream error: (Bug report) The SUID sandbox helper binary was found, but is not configured correctly · Issue #5333 · TriliumNext/Trilium · GitHub

8

I’ve found this page about a solution for SUID problem: What’s with chrome sandbox & electron? – Hacking and Learning

I’ve just set the owner and permissions as following: root:trilium 4755. Now I get the following error:

Jul 10 13:11:14 systemd[1]: Started trilium.service - Trilium: notes server.
Jul 10 13:11:14 trilium[2950727]: The setuid sandbox is not running as root. Common causes:
Jul 10 13:11:14 trilium[2950727]:   * An unprivileged process using ptrace on it, like a debugger.
Jul 10 13:11:14 trilium[2950727]:   * A parent process set prctl(PR_SET_NO_NEW_PRIVS, ...)
Jul 10 13:11:14 trilium[2950727]: Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
Jul 10 13:11:14 trilium[2950706]: [2950706:0710/131114.811952:FATAL:zygote_host_impl_linux.cc(207)] Check failed: . : Invalid argument (22)
Jul 10 13:11:14 systemd[1]: trilium.service: Main process exited, code=killed, status=5/TRAP
Jul 10 13:11:14 systemd[1]: trilium.service: Failed with result 'signal'.

EDIT

I tried another solution based on this article: Solve “The SUID sandbox helper binary was found, but is not configured correctly.” (3 solutions!) | by Authmane Terki | Medium

systemctl edit trilium and added the following lines:

[Service]
ExecStart=
ExecStart=/var/www/trilium/trilium --disable-gpu --no-sandbox

Started the service, it was almost going to start but… I get a display error:

Jul 10 14:13:36 systemd[1]: Started trilium.service - Trilium: notes server.
Jul 10 14:13:38 trilium[2961867]: (node:2961867) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
Jul 10 14:13:38 trilium[2961867]: (Use `trilium --trace-warnings ...` to show where the warning was created)
Jul 10 14:13:39 trilium[2961867]: Language option not found, falling back to en.
Jul 10 14:13:40 trilium[2961867]: Language option not found, falling back to en.
Jul 10 14:13:40 trilium[2961867]: Generated session secret
Jul 10 14:13:41 trilium[2961867]: DB not initialized, please visit setup page
Jul 10 14:13:41 trilium[2961867]: DB size: 4 KB
Jul 10 14:13:41 trilium[2961867]: {
Jul 10 14:13:41 trilium[2961867]:   "appVersion": "0.91.6",
Jul 10 14:13:41 trilium[2961867]:   "dbVersion": 228,
Jul 10 14:13:41 trilium[2961867]:   "nodeVersion": "v20.18.1",
Jul 10 14:13:41 trilium[2961867]:   "syncVersion": 34,
Jul 10 14:13:41 trilium[2961867]:   "buildDate": "2025-02-03T17:08:06Z",
Jul 10 14:13:41 trilium[2961867]:   "buildRevision": "79e830b6ea22e51196bdca4c021f30ecfad92723",
Jul 10 14:13:41 trilium[2961867]:   "dataDirectory": "/home/yunohost.app/trilium",
Jul 10 14:13:41 trilium[2961867]:   "clipperProtocolVersion": "1.0",
Jul 10 14:13:41 trilium[2961867]:   "utcDateTime": "2025-07-10T11:13:39.070Z"
Jul 10 14:13:41 trilium[2961867]: }
Jul 10 14:13:41 trilium[2961867]: CPU model: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz, logical cores: 4, freq: 0 Mhz
Jul 10 14:13:41 trilium[2961867]: Trusted reverse proxy: false
Jul 10 14:13:41 trilium[2961867]: App HTTP server starting up at port 37840
Jul 10 14:13:41 trilium[2961867]: Listening on port 37840
Jul 10 14:13:41 trilium[2961867]: [2961867:0710/141341.205839:ERROR:ozone_platform_x11.cc(246)] Missing X server or $DISPLAY
Jul 10 14:13:41 trilium[2961867]: [2961867:0710/141341.206120:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
Jul 10 14:13:41 systemd[1]: trilium.service: Main process exited, code=killed, status=11/SEGV

So, if it will be deployed as a server, it should be started in the sandbox, therefore this solution was for desktop applications :face_exhaling: