[
https://issues.apache.org/jira/browse/GUACAMOLE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper reopened GUACAMOLE-559:
--------------------------------------
Currently seeing the following with SSH:
{code:none}
Thread 2.4 "guacd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeb7fe700 (LWP 21927)]
guac_terminal_clipboard_reset (term=0x0, mimetype=0xe11ac0 "text/plain")
at terminal.c:1875
1875 guac_common_clipboard_reset(term->clipboard, mimetype);
(gdb) bt
#0 0x00007ffff2cf28c0 in guac_terminal_clipboard_reset (term=0x0,
mimetype=0xe11ac0 "text/plain") at terminal.c:1875
#1 0x00007ffff2ce7027 in guac_ssh_clipboard_handler (user=<optimized out>,
stream=0xe0c090, mimetype=<optimized out>) at clipboard.c:35
#2 0x00007ffff7bd1ce9 in guac_user_input_thread (data=<optimized out>)
at user-handshake.c:222
#3 0x00007ffff6ff150b in start_thread (arg=0x7fffeb7fe700)
at pthread_create.c:465
#4 0x00007ffff5adf16f in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
{code}
I believe this is due to a race condition where the terminal may not have been
allocated by the time the clipboard is sent from the client, and that this has
not happened in the past because there are typically no clipboard contents to
synchronize within the window this race condition applies. With support for the
Asynchronous Clipboard API, this is now much more likely to occur.
> Add support for the new Asynchronous Clipboard API
> --------------------------------------------------
>
> Key: GUACAMOLE-559
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-559
> Project: Guacamole
> Issue Type: Improvement
> Components: Documentation, guacamole, Website
> Reporter: Michael Jumper
> Assignee: Michael Jumper
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: async-clipboard-api.png
>
>
> As of very recently, there is a new "Asynchronous Clipboard API" available
> for allowing webapps like Guacamole to read/write the clipboard [pretty much
> *exactly* like we've always wanted|^async-clipboard-api.png]:
> [https://www.w3.org/TR/clipboard-apis/#async-clipboard-api]
> Users are prompted whether they wish to grant the page access, and their
> answer is remembered going forward just like the other various things users
> can grant access to (audio input, for example).
> This API is available in Chrome 66+:
> [https://developers.google.com/web/updates/2018/03/clipboardapi]
> A pair of flags must currently be enabled for the API to be available:
> * [chrome://flags/#enable-experimental-web-platform-features]
> * [chrome://flags/#clipboard-content-setting]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
