you're right in that it's not a X2Go issue. I got a workaround by creating a browsing profile in another directory than the default one (~/.config/chromium):

mkdir -p /tmp/chromium
chromium-browser --user-data-dir=/tmp/chromium

I now have a "local" profile, and a "remote" profile that I use if loggin through X2Go.
 
.Jose

On Mon, Dec 12, 2016 at 9:56 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 07.12.2016 um 22:29 schrieb Jose Borreguero:

> I find that if I have chromium running in the server, any attempt to
> open chromium in the x2go client session will result in a new window of
> the browser been opened in the server. Does anybody now how can avoid this?

I don't have a solution for this, but it seems to be a bad habit that
chromium shares with libreoffice/openoffice.  If you run multiple X2Go
sessions under the same user account, all libreoffice/openoffice windows
will open in the session where you opened the first
libreoffice/openoffice window.

IRRC, it is a long-standing known bug for LO/OO, but no one there has
bothered to fix it.  Maybe the chromium developers will respond faster?

Do you think you could reproduce it with multiple ssh -X sessions, so
the chromium devs won't blame X2Go and tag it WONTFIX?

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
http://lists.x2go.org/listinfo/x2go-user