search

Eeems-Org / oxide

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

Oxide crashing after closing xochitl and attempting to kill it(rM 2 only?) #327

Open FouzR opened 1 year ago

FouzR commented 1 year ago

Describe the bug The device hangs and then restarts Oxide launcher when you attempt to kill xochitl.

To Reproduce Steps to reproduce the behavior:

  1. Open xochitl through Oxide
  2. Go back to Oxide
  3. Hold the icon to show the kill option
  4. After which, it usually freezes, and then restarts Oxide

Expected behavior The kill option should've immediately closed xochitl without any crashes

Screenshots If applicable, add screenshots to help explain your problem.

Version Information:

Eeems commented 1 year ago

This is very likely a duplicate of #295

I have no plans for fixing this in the short term, as my current plan is to remove the chroot feature that seems to be the cause. Any extra information to validate if this is the chroot that is the issue or not would be helpful though.

FouzR commented 1 year ago

Aug 10 16:53:04 reMarkable tarnish[7587]: Stopping "/codes/eeems/oxide1/apps/d941cc3512975cd9beb7dde71108afce" Aug 10 16:53:04 reMarkable tarnish[7587]: Previous Applications ("codes.eeems.oxide") Aug 10 16:53:04 reMarkable xochitl[7587]: shutdown called Aug 10 16:53:04 reMarkable tarnish[7587]: Application "xochitl" crashed. Aug 10 16:53:04 reMarkable tarnish[7587]: Application "xochitl" is not running. Aug 10 16:53:04 reMarkable tarnish[7587]: Application "xochitl" exit code 15 Aug 10 16:53:04 reMarkable tarnish[7587]: Resuming "/codes/eeems/oxide1/apps/d3641f0572435f76bb5cc1468d4fe1db" Aug 10 16:53:04 reMarkable tarnish[7587]: Resumed "/codes/eeems/oxide1/apps/d3641f0572435f76bb5cc1468d4fe1db" Aug 10 16:53:04 reMarkable tarnish[7587]: Resuming previous application "codes.eeems.oxide" Aug 10 16:53:04 reMarkable tarnish[7587]: Previous Applications () Aug 10 16:53:04 reMarkable tarnish[7587]: Tearing down chroot "/tmp/tarnish-chroot/xochitl/chroot" Aug 10 16:53:04 reMarkable tarnish[7587]: QThread::wait: Thread tried to wait on itself Aug 10 16:53:04 reMarkable tarnish[7587]: QThread: Destroyed while thread is still running Aug 10 16:53:04 reMarkable systemd[1]: tmp-tarnish\x2dchroot-xochitl-chroot-var-volatile-tmp.mount: Succeeded. Aug 10 16:53:05 reMarkable systemd[1]: tarnish.service: Main process exited, code=killed, status=11/SEGV Aug 10 16:53:05 reMarkable systemd[1]: tarnish.service: Killing process 7645 (QQmlThread) with signal SIGKILL. Aug 10 16:53:05 reMarkable systemd[1]: tarnish.service: Killing process 8723 (Thread (pooled)) with signal SIGKILL. Aug 10 16:53:06 reMarkable systemd[1]: tarnish.service: Failed with result 'signal'. Aug 10 16:53:11 reMarkable systemd[1]: tarnish.service: Scheduled restart job, restart counter is at 3.

Not sure if this is helpful or not, but it's roughly around the point where the whole thing crashed

Eeems commented 1 year ago

There does seem to be some issues with what is happening there. My guess is that it has to do with the `/sys/power/state fifo thread for the chroot not shutting down properly, thus the QThread errors.