Bug 7651 - clipboardSend error when session is disconnected
Summary: clipboardSend error when session is disconnected
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-23 15:49 CET by Frida Flodin
Modified: 2021-06-08 12:53 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments
Screenshot of the error (40.07 KB, image/png)
2021-02-23 15:49 CET, Frida Flodin
Details

Description Frida Flodin cendio 2021-02-23 15:49:28 CET
Created attachment 977 [details]
Screenshot of the error

When a Web Access session is disconnected by the server we sometimes get the following error in the browser (see attachment):

Firefox:
> ThinLinc Web Access encountered an error:
> 
> TypeError: UI.rfb is undefined
> https://10.48.2.192:300/app/ui.js:970:9
> clipboardSend@https://10.48.2.192:300/app/ui.js:970:9

Chrome: 
> ThinLinc Web Access encountered an error:
> 
> Uncaught TypeError: Cannot read property 'clipboardPasteFrom' of undefined
> https://10.48.2.192:300/app/ui.js:970:16
> TypeError: Cannot read property 'clipboardPasteFrom' of undefined
>     at HTMLTextAreaElement.clipboardSend (https://10.48.2.192:300/app/ui.js:970:16)



I could not reproduce this all the time. I found one way to always reproduce:
* Session in Firefox on virtual machine (RHEL8)
* Open the Clipboard and write some text
* Terminating session by connecting with native client on my workstation (Fedora 32).

What I tried that didn't reproduce the issue:
* Session in Firefox on my workstation (Fedora 32)
* open the Clipboard and write some text 
* Terminating session by connecting with native client on my workstation (Fedora 32).


It does not seem to matter how the session is disconnected, if it is 'stolen' from another client (Web Access/native) or terminated by admin. I had to terminate the Web Access session from another machine, I could not reproduce the issue from only my workstation.

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