Giters

AsteroidOS / asteroid-launcher

AsteroidOS launcher and Wayland compositor based on Qt5, QML and QtWayland via Lipstick.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bug with alarm

tioui opened this issue · comments

commented

Hello,

I am making tests and is seems to have a bug when an alarm start when an app is open. When that happen, the alarm presenter is place on top and when the user press the Dismiss button of the alarm presenter, the launcher is shown. If you then try to start the app that was open again, it does not open anymore.

To reproduce:

  1. Create an alarm for the next minute in the "Alarm Clock" app.
  2. Start an app that does not automatically turn off (I use the flashlight)
  3. Wait for the alarm to ring
  4. Dismiss the alarm with the check button on the alarm presenter
  5. Try to start the app of the step 2 again

After the step 4, if I log with ssh on the watch, event if the launcher is shown, the "ps" command show that the app of the step 2 (in my case, the flashlight) is still on:

ceres@bass:~$ ps
...
  947 ceres     111m SN   /usr/bin/asteroid-flashlight
  966 ceres     2656 S    /usr/bin/invoker --single-instance --type=qtcomponents-qt5 /usr/bin/asteroid-flashlight
...

As we can see, invoker launch the app with the "--single-instance" option so, I assume that when the launcher try to start it again, it cannot because the app is already started. It looks like the app is still on, but not visible (so we cannot close it). To be able to launch it again, I have to kill it from ssh or restart the watch.