[
https://issues.apache.org/jira/browse/GUACAMOLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013386#comment-16013386
]
Michael Jumper commented on GUACAMOLE-125:
------------------------------------------
OK - this issue seems to be getting a lot of attention, so let me try to
clarify where this stands, and how testing needs to be done in general with
respect to such issues.
When it comes to unexpected behavior within the remote desktop inside a
Guacamole connection, reproducing the issue reliably is important, but that is
only the first step. The most important thing to understand is that if you are
encountering unexpected remote desktop behavior *there are two places where the
bug may reside*:
# Within Guacamole
# Within the protocol-specific library used by Guacamole to communicate with
the remote desktop (in this case FreeRDP)
There is no need to further confirm that this behavior is reproducible through
Guacamole. It clearly is. What needs to be determined is whether the same
behavior occurs within FreeRDP. Lacking that information, there is no progress
to be made here, because there is no place for a deeper investigation to begin
(and any effort expended doing so would be a waste).
I will try to find time to determine the above myself in the next few days, but
that's really the best I can do at the moment. If this bug is important to you,
and you want more attention given to it, here is the methodology I would
recommend when you perform your tests:
# Reproduce the bug using Guacamole, intentionally using a small screen size.
Again, the idea here is to cause the buggy session state, not to confirm that
the bug is reproducible in Guacamole. That much has been established.
# Connect using "xfreerdp", making sure to specify the exact same connection
parameters so you take over the same session. You should see Guacamole
disconnect - close the tab at that point so you don't end up in a reconnecting
war (Guacamole may automatically retry the connection after ~15 seconds).
# Move the RemoteApp window well outside the area where you saw Guacamole not
drawing things (measured from the upper-left corner of your monitor, the same
distance that the window would need to be from the upper-left corner of the
browser window when you used Guacmole).
# Interact with the RemoteApp window *such that things should be drawn within
the area affected by the bug*.
If things are not drawn as expected, then you have confirmed that the bug is
outside Guacamole, and there is nothing further to be done here (except
possible to confirm whether a more recent version of FreeRDP fixes things). If
things *are* drawn as expected, and you are absolutely positive that the window
was well within the buggy area relative to the upper-left corner of the
monitor, reconnect with Guacamole and recheck. If the bug comes back, then you
have confirmed that the bug is within Guacamole.
Please do not simply confirm whether you see this within Guacamole and stop
there. The question is not whether the problem can be reproduced with Guacamole
(it can). The question is whether the problem can be reproduced with FreeRDP's
"xfreerdp" client. Answering the latter narrows things significantly.
Thanks.
> 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: Minor
> Attachments: 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.3.15#6346)
