Currently a session is only restored when no process exists with the PID associated to that session. This can easily create issues when Kumo is closed by rebooting and a new process takes the old Kumo's PID on reboot.
One possible solution would be checking if that PID's executable is Kumo or not. However even then one would have to check the current process ID to ensure sessions are restored when coincidentally opening a new Kumo window with a PID matching an old Kumo session.
Currently a session is only restored when no process exists with the PID associated to that session. This can easily create issues when Kumo is closed by rebooting and a new process takes the old Kumo's PID on reboot.
One possible solution would be checking if that PID's executable is Kumo or not. However even then one would have to check the current process ID to ensure sessions are restored when coincidentally opening a new Kumo window with a PID matching an old Kumo session.