search

Eeems-Org / oxide

A desktop environment for the reMarkable tablet
https://oxide.eeems.codes
MIT License
251 stars 21 forks source link

No log output for applications that crash early #174

Open Eeems opened 3 years ago

Eeems commented 3 years ago

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.

Eeems commented 3 years ago

Perhaps manually emit readyReadStandardOutput and readyReadStandardError? https://github.com/Eeems/oxide/blob/master/applications/system-service/application.h#L399-L416

Eeems commented 1 year ago

Perhaps manually emit readyReadStandardOutput and readyReadStandardError? https://github.com/Eeems/oxide/blob/master/applications/system-service/application.h#L399-L416

I'm not sure that this actually helps when I've tried it