Handle errors from applications on desktop layer #2

Open
opened 2026-04-30 12:02:33 +00:00 by let_rec · 0 comments
Owner

Summary

We need to implement the feature which provides handling errors from desktop applications

Motivation

Now, Relago handles only system layer applications error from journal. But, we need to handle errors from application on desktop layer too.

What we did learn

You can see system services via this command:

systemctl list-units

To show units from user layer, you can use this:

systemctl --user list-units

Problem

We know how to handle various kinds of errors from system (e.g. OOM, Coredump, etc.). Since we know their structure, we can define their type signature easily. Now, we know nothing about user layer applications. But we know how to research and define it.

You can use their logs via this command:

journalctl --user -u <unit-name>

Learning sources

You can learn more about journal fields and layers from here: freedesktop.org/systemd.journal-fields

## Summary We need to implement the feature which provides handling errors from desktop applications ## Motivation Now, Relago handles only system layer applications error from journal. But, we need to handle errors from application on desktop layer too. ## What we did learn You can see system services via this command: ```bash systemctl list-units ``` To show units from user layer, you can use this: ```bash systemctl --user list-units ``` ## Problem We know how to handle various kinds of errors from system (e.g. OOM, Coredump, etc.). Since we know their structure, we can define their type signature easily. Now, we know nothing about user layer applications. But we know how to research and define it. You can use their logs via this command: ```bash journalctl --user -u <unit-name> ``` ### Learning sources You can learn more about journal fields and layers from here: [freedesktop.org/systemd.journal-fields](https://www.freedesktop.org/software/systemd/man/latest/systemd.journal-fields.html)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
xinux/relago#2
No description provided.