An update- the temp change I tried, commenting out line 95 in guacClientNotificatin.js worked (after rebuilding guac client)! Guac no longer tries to auto-reconnect after the vnc idle timeout. Here <https://drive.google.com/file/d/1DnOmEIW0cL3focmpKM4FDdjRwyHXeZe4/view?usp=sharing> is a screenshot of the new dialogue box that appears.
Nick- I still look forward to the changes you're thinking about- will be useful. But not as urgent now in case you're busy with other things (as I'm sure you are). Thanks everyone for the help! Tushar On Mon, Mar 14, 2022 at 5:41 PM Tushar Sheth <[email protected]> wrote: > Wow. Thank you! > > Let me know if there is anything I can do to help. Unfortunately though, > my skills are limited to being able to take code and manipulate it. > > Tushar > > On Mon, Mar 14, 2022 at 5:27 PM Nick Couchman <[email protected]> wrote: > >> On Mon, Mar 14, 2022 at 4:50 PM Tushar Sheth <[email protected]> >> wrote: >> >>> Thanks Jonathan- yes I have been looking at your various listserve posts >>> and github issues related to this. Very helpful. >>> >>> I'm unfortunately not skilled enough to make the full fix in vnc.c that >>> would mirror the changes to rdp.c that were made in response to your bug >>> submission. At least not quickly. >>> >>> Perhaps there is a temporary modification I can make to vnc.c- although >>> that seems a lot riskier than doing hacky things on the guac-client side :) >>> >>> >> Hello, everyone, >> As the reconnect is triggered on the client-side, I think it would be >> possible to create a Connection Attribute (as opposed to a parameter) to >> disable auto-reconnect and be able to set that per-connection, on any >> supported protocol. If I have some time in the coming days I'll take a stab >> at it. >> >> -Nick >> >>>
