I have a user who, upon connecting to an existing session, gets the following error: Too big cursor. After this the session terminates. The session has been running since November 16 and has had multiple succesful reconnection attempts with both the stable client and version 4.8.1. Due to https://www.cendio.com/bugzilla/show_bug.cgi?id=4516 the user upgraded the client to 4.9.0post build 5971, and has been using this client since November 30, and only today did the error occur. User downgraded to 4.8.1 and was able to reconnect to the session without error. I've asked the user to test 4.9.0 or the nightly to see if he still gets the same error after a successful connection from 4.8.1.
After the user had connected with 4.8.1 he could upgrade to 4.9.0 and connect without problems.
Thanks for the report. Bug 6961 describes a similar bug ("Rect too big"), which is also rarely seen. At this point, we do not know what is causing these bugs, but are grateful for any additional information.
You're welcome :) The user still has the session running -- is there anything I can do to supply you with more information that could aid in debugging this issue?
Since we don't know when this happens, it would be ideal if you could try to note down what you were doing when you get the bug. What applications you were using in the session, if it happened when a specific cursor expected, which platform the client is running on, etc.? If we could also get a client log with -d5 enabled we might get some useful information in there. Before you changed client versions back and forth, did the user get this error every time he tried to reconnect after that specific point? If so, I suspect this is related to what's running in the ThinLinc session. And in that case we should also have a look at the session logfile from the server: /var/opt/thinlinc/sessions/<USERNAME>/last/xinit.log
Created attachment 903 [details] xinit.log file for session starting on Nov 16 2018
The user is running Windows 10, the server is RHEL7 running ThinLinc server 4.8.0-5456. Yes, before we tried different client versions the user got the same error on every attempt. I think the user has been connecting to the session using both a single- and multi-monitor setup, if that's any help. The user is running Cadence Virtuoso in the session. I've attached the xinit.log file and will see if I can get the user to run the client with debugging enabled.
(In reply to comment #6) > The user is running Windows 10, the server is RHEL7 running ThinLinc server > 4.8.0-5456. > > Yes, before we tried different client versions the user got the same error on > every attempt. I think the user has been connecting to the session using both a > single- and multi-monitor setup, if that's any help. > > The user is running Cadence Virtuoso in the session. > > I've attached the xinit.log file and will see if I can get the user to run the > client with debugging enabled. Ok, thank you for the details. The log file is quite large and I can't see anything obvious. Do you have a timestamp around where the user saw the problem?
(In reply to comment #8) > Ok, thank you for the details. The log file is quite large and I can't see > anything obvious. Do you have a timestamp around where the user saw the > problem? The user first experienced the issues on November 29 around 11:27 CET. From my correspondence I can see that the user tried another ThinLinc client version and that it was working at 16:42. The same issue happened again on December 14 around 11:40. The user downgraded to 4.8.1 and could connect again some time around 14:18.
One thing to note is that downloading a nightly ThinLinc client is not expected to fix the issue reported in bug 4516. The issue was on the server side and I'm afraid you will have to wait for a proper ThinLinc 4.10.0 release to access that. We have had a look at the logfile as well. The issue you mentioned with "Too big cursor" and the 4.9.0post_build_5971 client is indicated in the log by connections that are immediately terminated. Unfortunately the log doesn't give us more details than that. Hopefully the client log that we are waiting for can give us something. Chances are however that the client log doesn't lead us to a full understanding. In this case we would have to find more details on when this happens. I have requested a demo of Cadence Virtuoso, if I'm granted that, would you be willing to share some instructions or files with which I can try to reproduce? In the meanwhile would you be willing to see for yourself if you can reproduce the same error as your user?
Have you been able to get a client log? Or tried to reproduce it yourself?
No update, so let's assume this is a variation of bug 6961. *** This bug has been marked as a duplicate of bug 6961 ***
