Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gnome-terminal + xpra start/attach issues #2010

Closed
totaam opened this issue Oct 26, 2018 · 10 comments
Closed

Gnome-terminal + xpra start/attach issues #2010

totaam opened this issue Oct 26, 2018 · 10 comments
Labels

Comments

@totaam
Copy link
Collaborator

totaam commented Oct 26, 2018

Issue migrated from trac ticket # 2010

component: clipboard | priority: major | resolution: duplicate

2018-10-26 14:49:41: stdedos created the issue


Continuing from #1997 for the gnome-terminal

I have the issue that
$ xpra start :30 --start-child=gnome-terminal --terminate-children=yes --exit-with-children=yes

fails most of the times, whereas
$ xpra start :30 --start-child=xterm --terminate-children=yes --exit-with-children=yes
starts correctly.

$ xpra start :30 --start-child=xterm --terminate-children=yes --exit-with-children=yes
and then gnome-terminal works all the time.

Bugs:

  1. After xpra start :30 [...] I need to xpra attach :30 [...]. Is that expected?

  • $ xpra start :30 --start-child=xterm --terminate-children=yes --exit-with-children=yes
  • Then start gnome-terminal
  • Disconnect
  • Reattach
  • gnome-terminal works, but sometimes (1 out of 7-10) xterm is frozen. Killing and re-attaching the xpra window fixes that
@totaam
Copy link
Collaborator Author

totaam commented Oct 26, 2018

2018-10-26 14:52:01: stdedos uploaded file xterm+gnome-terminal_freeze.zip (66.5 KiB)

@totaam
Copy link
Collaborator Author

totaam commented Oct 26, 2018

2018-10-26 17:21:47: antoine changed owner from antoine to stdedos

@totaam
Copy link
Collaborator Author

totaam commented Oct 26, 2018

2018-10-26 17:21:47: antoine commented


Please see ReportingBugs to provide additional information.

After xpra start :30 [...] I need to xpra attach :30 [...]. Is that expected?
Yes.
You can do all in one with --attach=yes.

but sometimes (1 out of 7-10) xterm is frozen
Do I need to start again or just detach + re-attach to trigger this?
Your log is full of:

Warning: more than 30 clipboard requests per second!

My guess is that you have a clipboard loop. Disable clipboard or disable the other tool that is doing the clipboard synchronization.
This is probably not a bug.

@totaam
Copy link
Collaborator Author

totaam commented Oct 29, 2018

2018-10-29 10:47:44: stdedos changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Oct 29, 2018

2018-10-29 10:47:44: stdedos set resolution to duplicate

@totaam
Copy link
Collaborator Author

totaam commented Oct 29, 2018

2018-10-29 10:47:44: stdedos commented


Replying to [comment:1 Antoine Martin]:

Please see ReportingBugs to provide additional information.

I understand that I am not good at bug reports. However, since I've taken xpra Information > Report Bug, I am not sure what did I miss.

$ xpra start goes from/to Ubuntu 16.04.5, but this is the only thing that comes to mind.

Do I need to start again or just detach + re-attach to trigger this?

Detach and re-attach is enough.

Your log is full of:

Warning: more than 30 clipboard requests per second!

My guess is that you have a clipboard loop. Disable clipboard or disable the other tool that is doing the clipboard synchronization.

Disabling the clipboard was helpful for this session. I am not sure how the loop works, but, I guess since I had other sessions open at the same time, maybe the sync was complicated?

There was no "external" connection; neither a shadow server. Only multiples of xterm, gnome-terminal

@totaam totaam closed this as completed Oct 29, 2018
@totaam
Copy link
Collaborator Author

totaam commented Oct 29, 2018

2018-10-29 10:56:23: antoine commented


I am not sure how the loop works, but, I guess since I had other sessions open at the same time, maybe the sync was complicated?
If any of the sessions is connected at either end (server or client) to a tool that abuses the X11 clipboard synchronization mechanism, you will see this problem.

The usual culprits are: synergy, virtualbox, clipboard managers, etc..

The better, long term solution for this is #812

@totaam
Copy link
Collaborator Author

totaam commented Nov 14, 2018

2018-11-14 22:56:09: stdedos commented


It happened again. Unfortunately, I have no replication instructions :/

I ran the command once, it gave me the empty window. I ran it again, and I collected all the diagnostics through that session :/

I hope the collected diagnostics are helpful

command

"C:\Program Files\Xpra\xpra_cmd" start ssh://user@ip/ --webcam=no --speaker=off --microphone=off --opengl=no --start=gnome-terminal

-Note that cliboard sync was on*. But it doesn't matter (I hope), because I got it happening 1 times out of 3~5, even with client clipboard off

"C:\Program Files\Xpra\xpra_cmd" start ssh://sntentos@172.16.57.121/ --webcam=no --cliboard=no --speaker=off --microphone=off --opengl=no --start=gnome-terminal

@totaam
Copy link
Collaborator Author

totaam commented Nov 14, 2018

2018-11-14 22:56:33: stdedos uploaded file trac_2010_new-attempt.zip (164.7 KiB)

@totaam
Copy link
Collaborator Author

totaam commented Nov 21, 2018

2018-11-21 14:44:10: antoine changed component from android to clipboard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant