Bug 7273 - user is not informed of why a session closes
Summary: user is not informed of why a session closes
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 1.3.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Pierre Ossman
Depends on: 171 7479
  Show dependency treegraph
Reported: 2018-11-05 10:35 CET by Pierre Ossman
Modified: 2022-01-17 10:40 CET (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2018-11-05 10:35:28 CET
Right now we don't give any information about why the client decides to close the session window. If this is the result of an active user choice¹ then this is probably correct. However there are many cases where it was unexpected for the user, and their only recourse in that case is to dig through the log file and try to understand the output there.

¹ Logging out, closing the window, etc.

Some possible cases:

 * Network issues (e.g. connection reset)
 * Server/remote desktop crash
 * Forced disconnect (idle timer, other client, etc.)
Comment 2 William Sjöblom cendio 2022-01-17 10:40:12 CET
When fixing bug 7479, there have been a couple of changes on this theme. These primarily relate to improved SSH error reporting as stated by the bug. Worth covering here, however, is that the changes introduced in the bug above also removed the short session error dialog for a couple of the "active choice" cases mentioned in comment 0:

- When signaling the client to stop (e.g. by pressing CTRL-C)
- On smart card removal if the ThinLinc client is configured to disconnect on smart card removal.

Note You need to log in before you can comment on or make changes to this bug.