xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #2649


Ignore:
Timestamp:
03/16/20 14:05:58 (2 months ago)
Author:
stdedos
Comment:

It's a weird request; but I'll go ahead anyway: Can you add diagnostics "of a higher level" than normal diagnostics, that would show:

  • clipboard sync start, origin: server/client, type: text/plain, data: data[100:]
  • clipboard sync done, type: text/plain

or equivalent? I know for you these are not "useful enough"; for me though would give a peace of mind that I did press cut/copy shortcut, and the status is OK/Fail.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2649

    • Property Summary changed from shadow clipboard ... again to clipboard syncing ... again
  • Ticket #2649 – Description

    initial v1  
    11Continuation from #2603:
    22
    3 I have no concurrent xpra sessions. Can you identify what's the issue here?
     3I have no concurrent xpra sessions - shadow or "normal client" are started by themselves. Can you identify what's the issue here?
    44
    5 Assuming it's the client's issue: Is there "some way" to keep polling who has/gets the clipboard lock?
     5Is there "some way" to keep polling who has/gets the clipboard lock? Kind of like the gtk-keyboard applet.
     6
     7''It does not appear to be shadow-specific''
     8