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

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

{quote}
Nick, I very much appreciate you identifying the root cause, and the 
resolution, for this issue.
{quote}
I don't think I'd say we've identified root cause, yet.  We've identified that 
the problem occurs with a specific version of FreeRDP, but not *why* it occurs. 
 I'm still going through the FreeRDP source code when I have time trying to 
figure out what xfreerdp does differently from Guacamole to see why xfreerdp 
works correctly.

{quote}
Would you have an opportunity to update those images to include the above 
referenced FreeRDP version which resolves this issue?
{quote}

Presumably the Docker image uses the Dockerfile in the Github repo, which just 
bases the image off the CentOS 7 core.  CentOS 7 ships with FreeRDP 1.0.2, so 
that's why that's the version bundled there.  I've successfully built 1.1.x on 
CentOS 7, so it'll work, I just don't know how much we want to deviate from 
what's available in the standard image - building custom code (other than our 
own, that is, the Guacamole code) inside the docker image adds another layer of 
stuff we have to manage (updates to the code, etc.), so, while it isn't all 
that difficult, it isn't all that trivial, either.  Additionally, it really 
would be nice to figure out what, specifically, about the way Guacamole invokes 
the RAIL plugin in 1.0.2 causes this behavior.  Anyway, I'll let Mike or James 
chime in as to whether they want to update the docker image to build the 
xfreerdp code from source instead of using RPMs.

> 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_detail.jpg, notepad_size_limit.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)

Reply via email to