x2go-dev March 2015

x2go-dev@lists.x2go.org

39 participants
196 discussions

Bug#789: This sounds grave
by Michael DePaulo 03 Mar '15

03 Mar '15

Control: severity -1 grave Control: affects -1 = x2goclient Control: tag -1 build-win32 HI Jozsef, Sorry to hear that you ran into this bug. I will look into it ASAP.

1 0

Reason for norootlessexit
by Ulrich Sibiller 02 Mar '15

02 Mar '15

Hello, we are seeing problems with rootless nx sessions, when the user is using a window manager like awesome, openbox or xfce (for users using kde or gnome everythign works fine). nxagent often closes the session after switching workspaces (making the nx windows invisible) because according to nxagent there's no client left (which is wrong). This can be prevented using -norootlessexit. However, I was wondering about the reason for this switch. Did anyone have similar problems and therefore added this switch? Uli

2 1

Bug#797: xinamera extension is broken after update
by Robert Reich 02 Mar '15

02 Mar '15

Package: x2goclient Version: 4.0.3.2-0~800~ubuntu14.04.1 xinamera extension is broken after update. Windows, panels etc maximize over two monitors Linux Mint 17.1 / Mate x2goclient_4.0.1.1-1ubuntu2_i386.deb still working flawlessly regards

2 2

Bug#802: pluma and caja launch successfully
by Michael DePaulo 02 Mar '15

02 Mar '15

I figured I'd try 2 other MATE apps as single applications: pluma (text editor) caja (file manager) They both launch successfully. The X2Go session wouldn't terminate when I X'd out of caja, but that is probably unrelated.

1 0

Bug#802: mate-terminal segfaults when launched as a single application
by Michael DePaulo 02 Mar '15

02 Mar '15

Package: x2goserver Version: 4.0.1.18 Severity: normal Client OS: Windows 10 64-bit (build 9926 with latest patches) x2goclient 4.0.3.2-21050301-debug Server OS: Fedora 21 64-bit with latest updates x2goagent.x86_64 3.5.0.28-1.fc21 @updates x2goserver.x86_64 4.0.1.18-5.fc21 @updates x2goserver-xsession.x86_64 4.0.1.18-5.fc21 @updates libNX_X11.x86_64 3.5.0.28-1.fc21 installed libNX_Xcomposite.x86_64 3.5.0.28-1.fc21 installed libNX_Xdamage.x86_64 3.5.0.28-1.fc21 installed libNX_Xdmcp.x86_64 3.5.0.28-1.fc21 installed libNX_Xext.x86_64 3.5.0.28-1.fc21 installed libNX_Xfixes.x86_64 3.5.0.28-1.fc21 installed libNX_Xinerama.x86_64 3.5.0.28-1.fc21 installed libNX_Xpm.x86_64 3.5.0.28-1.fc21 installed libNX_Xrandr.x86_64 3.5.0.28-1.fc21 installed libNX_Xrender.x86_64 3.5.0.28-1.fc21 installed libNX_Xtst.x86_64 3.5.0.28-1.fc21 installed nx-libs.x86_64 3.5.0.28-1.fc21 installed nxagent.x86_64 3.5.0.28-1.fc21 installed nxproxy.x86_64 3.5.0.28-1.fc21 installed I observed this on both the host OS (details above) and in a Fedora 21 64-bit docker container for X2Go that I am developing. When I launch mate-terminal from a MATE session, it opens and runs successfully. I can also launch uxterm as a Single application (seemless mode.) When I attempt to launch mate-terminal via any of these methods, it segfaults: Single application: mate-terminal Single application: Terminal Single application: uxterm (and then run "mate-terminal") I have attached the relevant lines from /var/log/messages (from the host OS.) (x2goserver has loglevel=debug) -Mike#2

1 0

Bug#801: Problem with session control in x2go
by Баев Илья 02 Mar '15

02 Mar '15

Package: x2go Version: 4.0.1.19 Linux Mint 13 Maya cups-x2go: 3.0.1.0x2goagent: 3.5.0.28x2goserver: 4.0.1.19x2goserver-extensions: 4.0.1.19x2goserver-printing: 4.0.1.19x2goserver-xsession: 4.0.1.19 Hello We have a problem with session control. When anybody try to use current sessions they all have been showing to him as "him_name"@session_number and hi can do anything with it despite his authentication.Every user can run xwininfo and see all sessions as his own sessions. eugeny@pcdir-mint13 ~ $ x2golistdesktops No protocol specifiedxwininfo: error: unable to open display ":0"No protocol specifiedxwininfo: error: unable to open display ":0"eugeny@:51eugeny@:50eugeny@pcdir-mint13 ~ $ su tunkiPassword: tunki@pcdir-mint13 /home/K-DOM/eugeny $ x2golistdesktopsNo protocol specifiedxwininfo: error: unable to open display ":0"No protocol specifiedxwininfo: error: unable to open display ":0"tunki@:51tunki@:50tunki@pcdir-mint13 /home/K-DOM/eugeny $

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev March 2015