On Thu, Jul 3, 2025 at 12:52 PM Jason Keltz <[email protected]> wrote:
> Hi.
> Yesterday, I tried to update my Guacamole 1.5.5 install to 1.6.0 when
> there were no users logged in to my guacamole server.
> This is on a RHEL 8.10 system where I do a self compile.
> After updating the system, I restarted guacd. All of a sudden, I noticed
> when trying to connect to any system (all also running RHEL8.10), the GNOME
> would sort of "freeze" mid login.
> I tried a few systems with the same behaviour. I had to quickly revert
> the system to using 1.5.5 so couldn't debug.
> Today, I setup a separate dev system for testing. I got 1.5.5 working,
> then did the same steps I did yesterday when upgrading the production
> server with 1.6.0.
> This time, oddly enough, it seems to be working which is very puzzling.
> The server is auto installed so the dev server is setup the same was as the
> production one.
> However, the problem I saw yesterday does not exist. I don't understand
> how that's possible.
> I was hoping to replicate the problem to give me an opportunity to debug.
>
This does sound very strange, and I'd also be very interested to figure out
what's going on. If you have a chance to restart your production guacd
instance with debug logging turned on ("-L debug" flag) and reproduce the
issues, I'd be interested to see if anything shows up in the logs.
> However, on another note, on 1.6.0, when I am moving windows around, they
> are leaving remnants on the background. Login to the same system with
> 1.5.5 does not do this.
> See the 1.6.0 image here after moving a terminal window around:
>
This is likely related to the re-working of the graphics code, although I
thought we had squashed all of those bugs prior to the full 1.6.0 release.
Can you confirm you're running the actual 1.6.0 (after 1.6.0-RC3) and not a
slightly earlier 1.6.0 release candidate (-RC1 or -RC2)? Otherwise we'll
likely need to open and track a bug for this.
-Nick
>
