Eeems-Org / Eeems-Org/oxide

No log output for applications that crash early

Open
#174 2 comments 0 reactions 1 assignee Claimed by @Eeems View on GitHub
📱 reMarkable 1 📱 reMarkable 2 bug
Dominant language
C
Stars
281
Forks
25
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If an application crashes quickly after startup, there is no log output captured.

**To Reproduce**
Steps to reproduce the behavior:
1. Add the autoStart flag to corrupt (task switcher)
2. Restart tarnish
3. Check logs (`journalctl -eu tarnish`) and you'll see that it reports codes.eeems.corrupt as crashing but there is no log output.

**Expected behavior**
The log output of the crashed application should be visible to assist with debugging.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.