You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Nick Couchman (JIRA)" <ji...@apache.org> on 2018/01/03 17:58:00 UTC

[jira] [Commented] (GUACAMOLE-125) Sometimes session is not initialised on Full screen

    [ https://issues.apache.org/jira/browse/GUACAMOLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309997#comment-16309997 ] 

Nick Couchman commented on GUACAMOLE-125:
-----------------------------------------

Copying a response that I posted to the Guacamole Dev mailing list:

{quote}
Well, I may have hit upon something, though I'm not certain, yet.  I decided to look at the
difference in the RAIL library between 1.0 and 1.1, since the problem exists in 1.0 but is
fixed in 1.1.  Take a look at the difference in these two pieces of code:

Stable-1.0: https://github.com/FreeRDP/FreeRDP/blob/b9fd0db009ac1bba19cf9049a7d556c120a03073/libfreerdp-rail/rail.c#L100

Stable-1.1: https://github.com/FreeRDP/FreeRDP/blob/03ab68318966c3a22935a02838daaea7b7fbe96c/libfreerdp/rail/rail.c#L109

The comment above the 1.1 version is particularly interesting - this method deals specifically
with screen locked situations, where there is a switch between RAIL monitoring the desktop
and not monitoring it...such as would happen when disconnecting/reconnecting to a RAIL session
with Guacamole.

I'm still wrapping my brain around the FreeRDP code, so does it look like I'm on the right
track at all?  I haven't dug into the xfreerdp code, yet, to see if there's a place there
where there's any sort of method or work-around for dealing with it.  
{quote}

So, not sure if this is where the issue actually exists or not, and, if so, if there's anything that can really be done about it??

> Sometimes session is not initialised on Full screen 
> ----------------------------------------------------
>
>                 Key: GUACAMOLE-125
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-125
>             Project: Guacamole
>          Issue Type: Bug
>    Affects Versions: 0.9.9, 0.9.10-incubating
>         Environment: Guacamole running on Debian 8.6
> Forwarding a windows 2012 R2 session
>            Reporter: Frank Giroud
>            Priority: Critical
>         Attachments: fj1.png, fj2.png, fj3.png, fj4.png, fj5.png, fj6.png, notepad_size_limit.jpg, notepad_size_limit_detail.jpg
>
>
> Sometimes after logging in (which happens to be Full scren) the windows session or the RemoteApp is not launched in full screen.
> In fact it behaves like there were a pseudo-resolution smaller than the required one.
> The browser (Chrome is open in a 1920*1200) but the screen displayed is locked to something like 1024*768 or so. 
> When you click on the Fullscreen button. It open and let a black screen all around in the web browser. .
> -The behavior is the same if you start a windows session , the windows desktop displayed in the web browser is in a 'smaller display' and what remains is black.- Haven't succeed to reproduce after all
> I have succeeded to find a way to reproduce the behavior "kind of" more often.
> In my example i configure notepad++ to be a remoteapp (launch by ||notepad in guacamole )
> # Launch a session through Guacamole => No probleme guacamole can be set in fullscreen (on all the browser window)
> # Unmaximized the application
> # Ctrl-Shift-Alt menu => Disconnect
> # On the guacamole option menu (3 choices) => Reconnect
> # The result => my screenshot



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)