Activity log for bug #1813491
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2019-01-27 18:34:59 | spikedboy | bug | added bug | ||
| 2019-01-27 18:58:58 | spikedboy | summary | PID is -1 after app.open() in linux based systems | [1.1.4] Linux: PID is -1 after app.open() | |
| 2019-01-28 12:02:18 | RaiMan | sikuli: status | New | Fix Committed | |
| 2019-01-28 12:02:24 | RaiMan | sikuli: importance | Undecided | High | |
| 2019-01-28 12:02:28 | RaiMan | sikuli: assignee | RaiMan (raimund-hocke) | ||
| 2019-01-28 12:02:32 | RaiMan | sikuli: milestone | 1.1.4 | ||
| 2019-03-23 08:52:01 | RaiMan | sikuli: status | Fix Committed | In Progress | |
| 2019-03-23 08:52:05 | RaiMan | sikuli: importance | High | Medium | |
| 2019-04-14 13:54:18 | RaiMan | sikuli: importance | Medium | High | |
| 2019-11-07 15:26:24 | RaiMan | description | When building an App object with the path to the executable, after calling app.open(), the PID is always -1. This causes app.isRunning() to run a ps shell comand with parameter "-1" which will not find the process, even if it ran. | see: https://github.com/RaiMan/SikuliX1/issues/144 -------------------------------------------------- When building an App object with the path to the executable, after calling app.open(), the PID is always -1. This causes app.isRunning() to run a ps shell comand with parameter "-1" which will not find the process, even if it ran. | |
| 2019-11-07 15:26:29 | RaiMan | sikuli: milestone | 1.1.4 | ||
| 2019-11-07 15:26:35 | RaiMan | sikuli: status | In Progress | Confirmed | |
| 2021-02-09 16:20:26 | RaiMan | sikuli: status | Confirmed | Fix Released | |
| 2021-02-09 16:20:40 | RaiMan | sikuli: status | Fix Released | Fix Committed | |
| 2021-02-09 16:20:45 | RaiMan | sikuli: importance | High | Critical | |
| 2021-02-09 16:20:58 | RaiMan | summary | [1.1.4] Linux: PID is -1 after app.open() | [1.1.4] Linux: PID is -1 after app.open() --- fixed 2.0.5 | |
| 2021-02-09 16:21:00 | RaiMan | sikuli: milestone | 2.0.5 |
