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

Nick Couchman edited comment on GUACAMOLE-2123 at 12/8/25 8:31 PM:
-------------------------------------------------------------------

Aaaaaaaaaaargh. I feel like I'm making minuscule progress, but every time I get 
one little thing sorted out I end up tripping over assertions in the display 
plan. Clearly I don't fully understand how it all works, but right now I'm 
alternately hitting one of the following assertions:

{{
GUAC_ASSERT in PFW_LFR_guac_display_plan_create() failed at display-plan.c:158.
GUAC_ASSERT in PFW_LFR_guac_display_plan_create() failed at display-plan.c:360.
}}
 
And in the rare instance that I'm not tripping one of those two assertions, I 
either get no display updates at all for the RAIL windows, or I get very 
oddly-sized and located updates (click a menu on one part of the screen and it 
updates somewhere else).

Any hints are welcome.

To provide a little more context...I've figured out that, if you have the GFX 
extension enabled, the normal BeginPaint and EndPaint routines do not get 
called, and, instead, updates are expected to be done through the 
RdpgfxClientContext->UpdateWindowFromSurface callback, with the idea being 
that, instead of updating the entire desktop/client area, you only update the 
window. I've got an initial implementation of that callback going, but I'm 
hitting the above assertions and not quite sure what I've done incorrectly.


was (Author: [email protected]):
{{Aaaaaaaaaaargh. I feel like I'm making minuscule progress, but every time I 
get one little thing sorted out I end up tripping over assertions in the 
display plan. Clearly I don't fully understand how it all works, but right now 
I'm alternately hitting one of the following assertions:}}

GUAC_ASSERT in PFW_LFR_guac_display_plan_create() failed at display-plan.c:158.

GUAC_ASSERT in PFW_LFR_guac_display_plan_create() failed at display-plan.c:360.

 

{{{}And in the rare instance that I'm not tripping one of those two assertions, 
I either get no display updates at all for the RAIL windows, or I get very 
oddly-sized and located updates (click a menu on one part of the screen and it 
updates somewhere else).{}}}{{{{}}{}}}

{{Any hints are welcome.}}

To provide a little more context...I've figured out that, if you have the GFX 
extension enabled, the normal BeginPaint and EndPaint routines do not get 
called, and, instead, updates are expected to be done through the 
RdpgfxClientContext->UpdateWindowFromSurface callback, with the idea being 
that, instead of updating the entire desktop/client area, you only update the 
window. I've got an initial implementation of that callback going, but I'm 
hitting the above assertions and not quite sure what I've done incorrectly.

> Remote App Windows not updated with GFX Pipeline
> ------------------------------------------------
>
>                 Key: GUACAMOLE-2123
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2123
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP
>    Affects Versions: 1.6.0
>            Reporter: Nick Couchman
>            Assignee: Nick Couchman
>            Priority: Blocker
>             Fix For: 1.6.1
>
>
> When using RemoteApp support with the GFX pipeline, the remote applications 
> are not updated properly. Disabling the GFX pipeline is an effective 
> work-around, but I suspect that a couple of callbacks need to be implemented 
> to force updates of the screen where the Remote App windows are.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to