View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003611 | gnunet-gtk | gnunet-conversation-gtk | public | 2015-01-16 11:10 | 2018-06-06 22:25 |
| Reporter | Christian Grothoff | Assigned To | yids | Due Date | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | Git master | ||||
| Target Version | 0.11.0pre66 | Fixed in Version | 0.11.0pre66 | ||
| Summary | 0003611: active call stats active if gnunet-conversation-service is stopped/terminated | ||||
| Description | When a call is active and the conversation service is stopped/terminated, the call stays in the 'active' state, even though it is very much dead (and even after the service is resumed, it won't be recovered as the service needs to do a fresh handshake and everything, and thus we cannot automatically reestablish the connection). What is interesting is that the command-line (gnunet-conversation) tool does update its state properly, so clearly there is just something wrong in how gnunet-conversation-gtk handles some API call. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-01-16 11:10 | Christian Grothoff | New Issue | |
| 2015-01-16 11:10 | Christian Grothoff | Status | new => assigned |
| 2015-01-16 11:10 | Christian Grothoff | Assigned To | => yids |
| 2015-01-16 11:33 | Christian Grothoff | Note Added: 0008798 | |
| 2015-01-16 11:48 | Christian Grothoff | Note Added: 0008799 | |
| 2015-01-16 11:48 | Christian Grothoff | Status | assigned => resolved |
| 2015-01-16 11:48 | Christian Grothoff | Fixed in Version | => 0.11.0pre66 |
| 2015-01-16 11:48 | Christian Grothoff | Resolution | open => fixed |
| 2015-01-16 11:48 | Christian Grothoff | Target Version | => 0.11.0pre66 |
| 2018-06-06 22:25 | Christian Grothoff | Status | resolved => closed |