-
My host OS must be Ubuntu due to the program I want to run; by the way, it is a Qt-based program.
*: CentOS and Ubuntu are physical machines As #3989, Ubuntu has Xdummy issue, so that I tried to build a xpra fedora container on the Ubuntu one, the dockerfile is attached in the end. From the log file, it seems like there is only an audio-related issue due to no D-bus in the docker. (Is D-bus the key point?) So let's continue, run However, the server log will throw Now we can By using
The full server log is attached in pastebin due to too long. If the Xpra is running outside of docker, even some unsupported OS (e.g. CentOS 7 for Xpra 5), the clipboard works fine with Qt. Thank you in advance and have a nice day. Xpra Dockerfile:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 13 replies
-
My initial guess would be that the packages installed are not the same, perhaps missing
This also points to the same problem. Your Docker installation probably installed the minimal packages and this did not include
Please include the full error message, preferably running the server with
Looks like the clipboard tool need updating for Gtk API changes. |
Beta Was this translation helpful? Give feedback.
-
For the ssh agent, I added -d clipboard,ssh for both client and server.
I do not have any ssh agent on Windows, maybe I just simply disable this feature.
And an interesting phenomenon is that if I disconnect Xpra client and reconnect, I will find the ssh connection is established. For the dbus, By And here is the new log, for the ssh, I will execute |
Beta Was this translation helpful? Give feedback.
-
I have new clues. I use one Fedora 38 VM and one Fedora 38 docker, install
But the Xpra in Docker doesn't have them. The logs are 7MB each, very large, and may have my personal information; so, they are not suitable for publishing here. |
Beta Was this translation helpful? Give feedback.
-
After upgrade cuda and nvidia driver from 12.1 to 12.2, this issue disappeared.
|
Beta Was this translation helpful? Give feedback.
After upgrade cuda and nvidia driver from 12.1 to 12.2, this issue disappeared.
I think it is related to cuda or nvidia or something that nvidia would change it during install cuda.
What I did is the following.
apt upgrade
,apt dist-upgrade
, andapt full-upgrade
. And then run xpra to test, we still can find this issue.apt full-upgrade
can not upgrade Nvidia cuda and its driver (do not know why), runapt install cuda
andapt autoremove
.