Hello,
My question is about not being able to copy and paste strings between two systems via X2Go. I have two systems which specifications are:
- on the one side, a Linux system:
- OS Debian (Buster)
- x2goserver (v.4.1.0.3-4)
- Openbox (v.3.6.1-8)
- on the other side, a Windows system:
- OS Windows (8.1 Pro)
- x2goclient (v.4.1.2.0-2018-06-22)
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards.
Léa
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Hi Paul,
Thank you for your answer. Using the control-shift-c method and then paste with control-v on Windows doesn't work for me. Instead, I used ":set mouse=" in Gvim before copying an pasting like Stefan Baur suggested. I think it solves my problem (until the next one :)
Best regards,
Léa
On 17/01/2020 6:45 PM, Paul Borowicz wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Yesterday 3.5.99.23 was released. So can you please retry with that version?
Uli
On Thu, Jan 30, 2020 at 1:00 AM Norm Green <norm.green@gemtalksystems.com> wrote:
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
How can I do that? I followed the below procedure and am still at 3.5.99.22. I assume that since .23 is "released" that the Arctica repo should be sufficient and I don't need the Arctica nightly repo.
https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
Norm Green
On 1/31/2020 12:15 AM, Ulrich Sibiller wrote:
Yesterday 3.5.99.23 was released. So can you please retry with that version?
Uli
On Thu, Jan 30, 2020 at 1:00 AM Norm Green <norm.green@gemtalksystems.com> wrote:
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
Here is the problem: as long as I copy and paste strings from the Windows system to a console (xterm) in the Linux system, it works fine. If I start, for example, "gvim foo.txt" which contains the string "foo", select "foo" with the mouse and try to paste it in a Gvim or a Notepad running on the Windows system, the string "foo" is not pasted in the Windows Gvim or Notepad. And starting from this point, I cannot copy and paste anything between the two systems. I have to close all the Windows in the Linux system, close the X2Go session and restart a new one to have copy and paste work again between the two systems. And, as soon as I open a document with Gvim in the Linux system, and try to copy and paste strings to and from it, it malfunctions again. Practically, it becomes very unhandy because I regularly need to copy and paste things that way between the two systems.
Can you help me solve that problem? Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Well, I don't know when new packages are built and if that happens automatically. Mike, who did the release, did that during a train ride. Maybe he did not have enough time or not the infrastructure it needs.
Nevertheless there are nighlies fo 3.5.99.23: http://packages.arctica-project.org/debian-nightly/pool/main/n/nx-libs/ (see also https://sunweavers.net/blog/node/20)
Uli
On Fri, Jan 31, 2020 at 8:16 PM Norm Green <norm.green@gemtalksystems.com> wrote:
How can I do that? I followed the below procedure and am still at 3.5.99.22. I assume that since .23 is "released" that the Arctica repo should be sufficient and I don't need the Arctica nightly repo.
https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
Norm Green
On 1/31/2020 12:15 AM, Ulrich Sibiller wrote:
Yesterday 3.5.99.23 was released. So can you please retry with that version?
Uli
On Thu, Jan 30, 2020 at 1:00 AM Norm Green <norm.green@gemtalksystems.com> wrote:
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Léa!
Am 15.01.20 um 12:08 schrieb Lmhelp1:
> Here is the problem: > as long as I copy and paste strings from the Windows system to a console > (xterm) in the Linux system, it works fine. > If I start, for example, "gvim foo.txt" which contains the string "foo", > select "foo" with the mouse and try to paste it in a Gvim or a Notepad > running on the Windows system, the string "foo" is not pasted in the > Windows Gvim or Notepad. > And starting from this point, I cannot copy and paste anything between > the two systems. > I have to close all the Windows in the Linux system, close the X2Go > session and restart a new one to have copy and paste work again between > the two systems. > And, as soon as I open a document with Gvim in the Linux system, and try > to copy and paste strings to and from it, it malfunctions again. > Practically, it becomes very unhandy because I regularly need to copy > and paste things that way between the two systems. > > Can you help me solve that problem? > Thanks and best regards. First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Uli,
Copy and paste seems better since moving to nx 3.5.99.23. I've been using it for about a week and haven't (yet) seen any of the previous problems, but it's a bit soon to declare complete victory.
Norm
On 2/1/2020 4:25 AM, Ulrich Sibiller wrote:
Well, I don't know when new packages are built and if that happens automatically. Mike, who did the release, did that during a train ride. Maybe he did not have enough time or not the infrastructure it needs.
Nevertheless there are nighlies fo 3.5.99.23: http://packages.arctica-project.org/debian-nightly/pool/main/n/nx-libs/ (see also https://sunweavers.net/blog/node/20)
Uli
On Fri, Jan 31, 2020 at 8:16 PM Norm Green <norm.green@gemtalksystems.com> wrote:
How can I do that? I followed the below procedure and am still at 3.5.99.22. I assume that since .23 is "released" that the Arctica repo should be sufficient and I don't need the Arctica nightly repo.
https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
Norm Green
On 1/31/2020 12:15 AM, Ulrich Sibiller wrote:
Yesterday 3.5.99.23 was released. So can you please retry with that version?
Uli
On Thu, Jan 30, 2020 at 1:00 AM Norm Green <norm.green@gemtalksystems.com> wrote:
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm on openSuse. I've always have trouble cutting and pasting between next to go and Windows using the mouse.
I usually have pretty good success if I copy from x to go using the control-shift-c method and then paste with control-v on Windows.
On Fri, Jan 17, 2020, 9:42 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote: > Hi Léa! > > Am 15.01.20 um 12:08 schrieb Lmhelp1: > >> Here is the problem: >> as long as I copy and paste strings from the Windows system to a console >> (xterm) in the Linux system, it works fine. >> If I start, for example, "gvim foo.txt" which contains the string "foo", >> select "foo" with the mouse and try to paste it in a Gvim or a Notepad >> running on the Windows system, the string "foo" is not pasted in the >> Windows Gvim or Notepad. >> And starting from this point, I cannot copy and paste anything between >> the two systems. >> I have to close all the Windows in the Linux system, close the X2Go >> session and restart a new one to have copy and paste work again between >> the two systems. >> And, as soon as I open a document with Gvim in the Linux system, and try >> to copy and paste strings to and from it, it malfunctions again. >> Practically, it becomes very unhandy because I regularly need to copy >> and paste things that way between the two systems. >> >> Can you help me solve that problem? >> Thanks and best regards. > First, do you really have to close the X2Go session? I would have > expected that suspending it, closing X2GoClient on Windows, and > restarting it would be enough to reset the clipboard. > > Second, there have been some changes to vim regarding the handling of > mouse commands, I believe this started with the version shipped with > Debian Stretch and got even worse in Buster. Maybe try: > > :set mouse= > > in gvim before trying to copy-paste things? > > Third, we are currently beta-testing a new version of the NX libraries > with numerous clipboard fixes. Please visit > <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see > if you can help us test the new version, so it can become a part of X2Go > proper. > > Kind Regards, > Stefan Baur > > -- > BAUR-ITCS UG (haftungsbeschränkt) > Geschäftsführer: Stefan Baur > Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 > Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 > _______________________________________________ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again.
Norm
On 2/12/2020 4:01 PM, Norm Green wrote:
Uli,
Copy and paste seems better since moving to nx 3.5.99.23. I've been using it for about a week and haven't (yet) seen any of the previous problems, but it's a bit soon to declare complete victory.
Norm
On 2/1/2020 4:25 AM, Ulrich Sibiller wrote:
Well, I don't know when new packages are built and if that happens automatically. Mike, who did the release, did that during a train ride. Maybe he did not have enough time or not the infrastructure it needs.
Nevertheless there are nighlies fo 3.5.99.23: http://packages.arctica-project.org/debian-nightly/pool/main/n/nx-libs/ (see also https://sunweavers.net/blog/node/20)
Uli
On Fri, Jan 31, 2020 at 8:16 PM Norm Green <norm.green@gemtalksystems.com> wrote:
How can I do that? I followed the below procedure and am still at 3.5.99.22. I assume that since .23 is "released" that the Arctica repo should be sufficient and I don't need the Arctica nightly repo.
https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
Norm Green
On 1/31/2020 12:15 AM, Ulrich Sibiller wrote:
Yesterday 3.5.99.23 was released. So can you please retry with that version?
Uli
On Thu, Jan 30, 2020 at 1:00 AM Norm Green <norm.green@gemtalksystems.com> wrote:
I am running the new nx libs 3.5.99.22 on Unbutu 16.04 and access the Linux machine from a windows 7 machine running x2go client 4.1.2.0 . Just now I cannot copy from the Linux desktop and paste on the windows side. Copy on goes fine but paste on the windows side shows an empty clipboard. I've tried the same 3 times with the same results. I'm guessing if I restart my x2go session that copy and paste it will work once again.
In any case, the copy and paste problems are not all fixed by the new nx libs.
Norm Green
On 1/22/2020 3:51 AM, Ulrich Sibiller wrote:
As Stefan already wrote: there have been a lot of clipboard improvements lately. They will be included in the next nx-libs release (would probably be 3.5.99.23). Unfortunately the current development version suffers from a serious crash so I cannot recommend you to try that one. A fix is available but has not been included yet - unfortunately.
Can you please try nx 3.5.99.22 from the location described here: https://sunweavers.net/blog/node/57
Uli
On Fri, Jan 17, 2020 at 6:45 PM Paul Borowicz <paul@borowicz.org> wrote: > I'm on openSuse. I've always have trouble cutting and pasting > between next to go and Windows using the mouse. > > I usually have pretty good success if I copy from x to go using > the control-shift-c method and then paste with control-v on > Windows. > > On Fri, Jan 17, 2020, 9:42 AM Stefan Baur > <X2Go-ML-1@baur-itcs.de> wrote: >> Hi Léa! >> >> Am 15.01.20 um 12:08 schrieb Lmhelp1: >> >>> Here is the problem: >>> as long as I copy and paste strings from the Windows system to >>> a console >>> (xterm) in the Linux system, it works fine. >>> If I start, for example, "gvim foo.txt" which contains the >>> string "foo", >>> select "foo" with the mouse and try to paste it in a Gvim or a >>> Notepad >>> running on the Windows system, the string "foo" is not pasted >>> in the >>> Windows Gvim or Notepad. >>> And starting from this point, I cannot copy and paste anything >>> between >>> the two systems. >>> I have to close all the Windows in the Linux system, close the >>> X2Go >>> session and restart a new one to have copy and paste work >>> again between >>> the two systems. >>> And, as soon as I open a document with Gvim in the Linux >>> system, and try >>> to copy and paste strings to and from it, it malfunctions again. >>> Practically, it becomes very unhandy because I regularly need >>> to copy >>> and paste things that way between the two systems. >>> >>> Can you help me solve that problem? >>> Thanks and best regards. >> First, do you really have to close the X2Go session? I would have >> expected that suspending it, closing X2GoClient on Windows, and >> restarting it would be enough to reset the clipboard. >> >> Second, there have been some changes to vim regarding the >> handling of >> mouse commands, I believe this started with the version shipped >> with >> Debian Stretch and got even worse in Buster. Maybe try: >> >> :set mouse= >> >> in gvim before trying to copy-paste things? >> >> Third, we are currently beta-testing a new version of the NX >> libraries >> with numerous clipboard fixes. Please visit >> <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> >> and see >> if you can help us test the new version, so it can become a >> part of X2Go >> proper. >> >> Kind Regards, >> Stefan Baur >> >> -- >> BAUR-ITCS UG (haftungsbeschränkt) >> Geschäftsführer: Stefan Baur >> Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 >> Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 >> _______________________________________________ >> x2go-user mailing list >> x2go-user@lists.x2go.org >> https://lists.x2go.org/listinfo/x2go-user > _______________________________________________ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Thu, Feb 13, 2020 at 1:10 AM Norm Green <norm.green@gemtalksystems.com> wrote:
....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again.
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Uli
Am 13.02.20 um 09:53 schrieb Ulrich Sibiller:
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Do you think we could add some kind of workaround that "zaps" the clipboard(s) on both ends? Kind of like how you "zap" a heart with a defibrillator when it goes into ventricular fibrillation. While that wouldn't fix the issue, it would allow the user to continue without having to suspend and resume the session - plus we might be able to gather clipboard content info for a bugreport that way. I'm thinking of a "hexdump -C"-like output that gets stored to a file on each end and that the user could submit if there's nothing confidential in it.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Thu, Feb 13, 2020 at 10:07 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 13.02.20 um 09:53 schrieb Ulrich Sibiller:
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Do you think we could add some kind of workaround that "zaps" the clipboard(s) on both ends? Kind of like how you "zap" a heart with a defibrillator when it goes into ventricular fibrillation. While that wouldn't fix the issue, it would allow the user to continue without having to suspend and resume the session - plus we might be able to gather clipboard content info for a bugreport that way. I'm thinking of a "hexdump -C"-like output that gets stored to a file on each end and that the user could submit if there's nothing confidential in it.
I deeply doubt that the clipboard CONTENT is responsible for the problems. That's merely a problem in the workflow.
My approach is rather adding a debug facility that can be enabled at runtime instead of compile time so that a user can enable it as needed.
A zapping keystroke could be implemented but I really consider as a temporary. I'd love to see the problems vanish altogether...
Uli
Am 13.02.20 um 10:16 schrieb Ulrich Sibiller:
Am 13.02.20 um 09:53 schrieb Ulrich Sibiller:
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help? Do you think we could add some kind of workaround that "zaps" the clipboard(s) on both ends? Kind of like how you "zap" a heart with a defibrillator when it goes into ventricular fibrillation. While that wouldn't fix the issue, it would allow the user to continue without having to suspend and resume the session - plus we might be able to gather clipboard content info for a bugreport that way. I'm thinking of a "hexdump -C"-like output that gets stored to a file on each end and that the user could submit if there's nothing confidential in it. I deeply doubt that the clipboard CONTENT is responsible for the
On Thu, Feb 13, 2020 at 10:07 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote: problems. That's merely a problem in the workflow.
Are you sure? Some reports I received (though I'm still waiting for the final test results) hinted that special characters might be triggering it. Things outside the 7-Bit or 7-Bit+usual-Windows-codepage range. Things like accented characters or "unusual" whitespace (not a mere blank, \t, \r, or \n, of course).
My approach is rather adding a debug facility that can be enabled at runtime instead of compile time so that a user can enable it as needed.
A zapping keystroke could be implemented but I really consider as a temporary. I'd love to see the problems vanish altogether...
The thing is, if you log the content of the clipboard(s) on both ends *before* you zap, that info might help you with debugging this. Think of it as a "clipboard coredump".
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Thu, Feb 13, 2020 at 10:55 AM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
I deeply doubt that the clipboard CONTENT is responsible for the problems. That's merely a problem in the workflow.
Are you sure? Some reports I received (though I'm still waiting for the final test results) hinted that special characters might be triggering it. Things outside the 7-Bit or 7-Bit+usual-Windows-codepage range. Things like accented characters or "unusual" whitespace (not a mere blank, \t, \r, or \n, of course).
Well, I argue from the code side. And there the content cannot influence the workflow. But I am only talking about the clipboard code in nxagent. Maybe we face a bug in the nxcomp lib here. Or in the vcxsrv clipboard code.
My approach is rather adding a debug facility that can be enabled at runtime instead of compile time so that a user can enable it as needed.
A zapping keystroke could be implemented but I really consider as a temporary. I'd love to see the problems vanish altogether...
The thing is, if you log the content of the clipboard(s) on both ends *before* you zap, that info might help you with debugging this. Think of it as a "clipboard coredump".
Of course it does not hurt. The corresponding dumping code is already there. I think I will implement the "zap" the next days.
Uli
On Thu, Feb 13, 2020 at 09:53:29AM +0100, Ulrich Sibiller wrote:
On Thu, Feb 13, 2020 at 1:10 AM Norm Green <norm.green@gemtalksystems.com> wrote:
....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again.
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Yep this workaround has always succeeded for me.o
But Norm is right, copy-paste subsystem does get intermittently derailed.
-- Leho Kraav, senior technology & digital marketing architect
P.S. Get a free course of your choice from CXL Institute with your CXL Live 2020 ticket. See the lineup here: https://cxl.com/live/
On 2020-02-13 11:09, Leho Kraav wrote:
On Thu, Feb 13, 2020 at 09:53:29AM +0100, Ulrich Sibiller wrote: On Thu, Feb 13, 2020 at 1:10 AM Norm Green <norm.green@gemtalksystems.com> wrote: ....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again. Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Yep this workaround has always succeeded for me.o
But Norm is right, copy-paste subsystem does get intermittently derailed.
I've switched from VcxSrv to Mobaxterm because of this clipboard problem with the Windows client.
Best regards,
Aki
On Tue, Feb 18, 2020 at 3:18 PM Aki Ketolainen <akik@mykolab.com> wrote:
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Yep this workaround has always succeeded for me.o
But Norm is right, copy-paste subsystem does get intermittently derailed.
I've switched from VcxSrv to Mobaxterm because of this clipboard problem with the Windows client.
Which indicates that VcXsrv is the culprit, not NX.
Uli
What command line options do you use when starting Mobaxterm for x2go ?
On 2/13/2020 1:17 AM, Aki Ketolainen wrote:
On 2020-02-13 11:09, Leho Kraav wrote:
On Thu, Feb 13, 2020 at 09:53:29AM +0100, Ulrich Sibiller wrote:
On Thu, Feb 13, 2020 at 1:10 AM Norm Green <norm.green@gemtalksystems.com <mailto:norm.green@gemtalksystems.com>> wrote:
....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again.
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Yep this workaround has always succeeded for me.o
But Norm is right, copy-paste subsystem does get intermittently derailed.
I've switched from VcxSrv to Mobaxterm because of this clipboard problem with the Windows client.
Best regards,
Aki
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On 2020-02-20 01:59, Norm Green wrote:
What command line options do you use when starting Mobaxterm for x2go ?
On 2/13/2020 1:17 AM, Aki Ketolainen wrote:
On 2020-02-13 11:09, Leho Kraav wrote: On Thu, Feb 13, 2020 at 09:53:29AM +0100, Ulrich Sibiller wrote: On Thu, Feb 13, 2020 at 1:10 AM Norm Green <norm.green@gemtalksystems.com> wrote: ....and of course as soon as I sent this email the copy and paste problem occurs on 3.5.99.23!
Summary: copy text from a windows app and paste to the x2go Linux desktop stops working. I verified the data is in the window clipboard by pasting it into a different windows app.
copy and paste starts working again once I restart the windows x2go session and copy the data to the windows clipboard again. Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Yep this workaround has always succeeded for me.o
But Norm is right, copy-paste subsystem does get intermittently derailed.
I've switched from VcxSrv to Mobaxterm because of this clipboard problem with the Windows client.
Best regards,
Aki
I use these settings in x2goclient.exe (Mobaxterm installs into your Documents directory in your home directory by default):
use custom X-Server: C:/Users/aki/Documents/MobaXterm/slash/bin/XWin_MobaX.exe
command line options: -clipboard -multiwindow -nowgl
Best regards,
Aki
Hi Uli,
I will try your suggestion the next time the problem occurs.
FWIW, my perception is 3.5.99.23 has fewer clipboard problems than the previous releases. Perhaps some but not all clipboard bugs were fixed?
Norm
On 2/13/2020 12:53 AM, Ulrich Sibiller wrote:
Sorry about that. One workaround might be to copy something to clipboard on the linux side and then on Windows again. Does that help?
Uli
On Thu, Feb 13, 2020 at 4:12 PM Norm Green <norm.green@gemtalksystems.com> wrote:
I will try your suggestion the next time the problem occurs.
Please report if it helped!
FWIW, my perception is 3.5.99.23 has fewer clipboard problems than the previous releases. Perhaps some but not all clipboard bugs were fixed?
Yeah, I have fixed some. And I have added many FIXMEs that point to possible improvements. But that's a whole lot of work and testing....
Uli
On Thu, Feb 13, 2020 at 4:17 PM Ulrich Sibiller <uli42@gmx.de> wrote:
On Thu, Feb 13, 2020 at 4:12 PM Norm Green <norm.green@gemtalksystems.com> wrote:
I will try your suggestion the next time the problem occurs.
Please report if it helped!
FWIW, my perception is 3.5.99.23 has fewer clipboard problems than the previous releases. Perhaps some but not all clipboard bugs were fixed?
Yeah, I have fixed some. And I have added many FIXMEs that point to possible improvements. But that's a whole lot of work and testing....
FWIW: I have added a keystroke that dumps the clipboard state to the logfile. Here's the corresponding tree: https://github.com/uli42/nx-libs/commit/89cac32d923c
This will (hopefully) hit the upstream eventually. For now you need to compile this yourself on Linux.
I have also started the "zap" feature but it turns out that some careful thinking is required here. I did not have the clearness yesterday to implement that ;-)
Uli
Uli
Reversing the process (copying from Linux and pasting on Windows) did not help. The only thing that helped was restarting the windows x2go session. Seems like x2go randomly stops accepting data from the windows clipboard until it is restarted.
On 2/13/2020 7:17 AM, Ulrich Sibiller wrote:
On Thu, Feb 13, 2020 at 4:12 PM Norm Green <norm.green@gemtalksystems.com> wrote:
I will try your suggestion the next time the problem occurs. Please report if it helped!
FWIW, my perception is 3.5.99.23 has fewer clipboard problems than the previous releases. Perhaps some but not all clipboard bugs were fixed? Yeah, I have fixed some. And I have added many FIXMEs that point to possible improvements. But that's a whole lot of work and testing....
Uli
Hi Stefan,
Sorry for my late answer.
I am not sure, now, that I "closed the X2Go session" ; maybe I didn't, I'm not sure how to do that. However, for sure, I closed the X2GoClient on Windows and restarted it. But to answer your question, closing the X2GoClient on Windows and restarting it doesn't make things rework afterwards (maybe contrary to what I wrote before).
Launching ":set mouse=" in Gvim before copying and pasting, like you suggested, actually solves my problem :) I put this command in ".vimrc".
Thank you and best regards,
Léa
On 17/01/2020 3:42 PM, Stefan Baur wrote:
First, do you really have to close the X2Go session? I would have expected that suspending it, closing X2GoClient on Windows, and restarting it would be enough to reset the clipboard.
Second, there have been some changes to vim regarding the handling of mouse commands, I believe this started with the version shipped with Debian Stretch and got even worse in Buster. Maybe try:
:set mouse=
in gvim before trying to copy-paste things?
Third, we are currently beta-testing a new version of the NX libraries with numerous clipboard fixes. Please visit <https://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting> and see if you can help us test the new version, so it can become a part of X2Go proper.
Kind Regards, Stefan Baur
-
Aki Ketolainen -
Leho Kraav -
Lmhelp1 -
Norm Green -
Paul Borowicz -
Stefan Baur -
Ulrich Sibiller