Bug 2651 - Wrong reconnect handling for no-sessions, no-allowed, ask-policy
Summary: Wrong reconnect handling for no-sessions, no-allowed, ask-policy
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Pierre Ossman
Keywords: interesting_210
Depends on:
Reported: 2008-01-23 20:27 CET by Peter Åstrand
Modified: 2019-04-02 12:50 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2008-01-23 20:27:57 CET
As documented by multisession-reconnect.txt:

         No connected       
         No disconnected    
1.            C/X(1) 
2.            C/X(1) 

That is: If you don't have any sessions at all, matching the specified command, and you are not allowed to create any new sessions, you should get an error message. Currently, this is done for policy 1. In the Ask policy, however, you are reconnected automatically, even though the command does not match. Also, perhaps you should get an Ask dialog instead. 

I do not believe that this is 2.0.0 critical.
Comment 1 Peter Åstrand cendio 2008-01-23 20:30:14 CET
When we are implementing this bug, we might want to clean up the tlclient implementation as well. 

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