x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Heads-Up: X2Go: The Gathering 2017 will be taking place 2017-09-22 to 2017-09-24
by Stefan Baur 29 May '17

29 May '17

+++ Attention +++ Attention +++ Attention +++ Attention +++ X2Go: The Gathering 2017 will be taking place 2017-09-22 to 2017-09-24 We currently have two possible locations (Linuxhotel, and a hacker space in the southwest of Germany) that already confirmed they can host our event in the given timeframe, and are currently evaluating a third (in the city where X2Go was created, Treuchtlingen, Germany). A Wiki page with all available options will get linked and mentioned on the X2Go-Project Mailing List shortly after 2017-05-15 (our Decision Day for the Treuchtlingen location), along with a list of Pros and Cons for each location. We intend to have a public vote amongst all potential participants regarding the location from when said wiki page goes live until 2017-06-15. Note that we reserve the right to deviate from the poll result if it turns out that it would mean an undue hardship for one or more of the core X2Go team members or our sponsors, or if something happens after the end of the polling timeframe that requires us to reconsider, like, a location suddenly increasing prices, strikes, natural disasters, etc. Please mark the date in your calendars already, as while we haven't decided on the location yet, *the date is fixed* - as it is the only weekend where we have enough "critical mass" regarding the core X2Go team members. 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

1 1

Bug#1180: "Failed to restore all the required visuals" when switching from VcXsrv 1.19.2.0 to 1.17.0.0-3
by Mike DePaulo 28 May '17

28 May '17

Package: x2goclient Version: 4.1.0.0 Tags: +build-win32 When you do the following: 1. Replace x2goclient's VcXsrv folder with that upstream VcXsrv 1.19.2.0 2. Start an X2Go session 3. Suspend the session. 4. Replace x2goclient's VcXsrv folder with its default version, 1.17.0.0-3 (X2Go/Arctica builds) 5. Reconnect & resume the X2Go session You get the error message: Failed to restore all the required visuals And the session fails to resume. Yes, this is the same symptom as bug #891, but under different circumstances. https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=891 I am sure it could be reproduced if you were to specify VcXsrv 1.19.2.0 as an external X server instead. Server: RHEL 7.3 with EPEL's x2goserver 4.0.1.20-1.el7 & nxagent 3.5.0.32-3.el7 & xfce 4.12.1 Client System: Windows 10 1703 x64

2 1

Bug#1181: Unable to logout of KDE4 when a PolicyKit prompt is up
by Mike DePaulo 27 May '17

27 May '17

Package: nx-libs Version: 3.5.0.32 Note: This bug might actually be in x2goserver instead. Steps: 1. You connect to a KDE4 server 2. You maximize the session 3. #2 This triggers a PolicyKit prompt "Authentication is required to create a color managed device" 4. You select to log out of KDE 5. The screen does not turn black. There is a log out dialog, but it is actually hidden behind the PolicyKit prompt. 6. You are unable to click the log out button in the log out dialog because it is not visible. Hitting escape does not help either. You are unable to move the PolicyKit prompt. Note: In the absence of the PolicyKit dialog, the screen still does not turn black. Note: #3. Is a nuisance in and of itself. It is related to the fact that PolicyKit applies different rules for physical logins (active) vs remote logins (inactive.) It is especially a nuisance because you have to click "cancel" repeatedly. However, it is not what I am reporting as a bug. If you have a local session, this bug does not occur: 3. Trigger a PolicyKit prompt by opening up a terminal and running `pkexec vi` for example. 5. The screen turns black, and the log out dialog appears. 6. You click the log out button and all is well. This can be worked around by moving the PolicyKit prompt before logging out, or by hitting "cancel" repeatedly. I am confident this can be worked around also by writing new PolicyKit rules that prevent the "color managed device" prompt. I will post how soon. However, other PolicyKit prompts can presumably still cause this issue. Server configuration 1: CentOS 7.3 with KDE4 & EPEL's x2goserver 4.0.1.20-1.el7 & nxagent 3.5.0.32-3.el7 Server configuration 2: CentOS 7.3 with KDE4 & nightly x2goserver 4.1.0.0 & nxagent 3.5.99.7 (from the copr repo mikedep333/nx-libs-3.6) Client 1: Fedora 25 x64 with Fedora's x2goclient 4.1.0.0-1.fc25 & nxproxy 3.5.0.32-4.fc24 Client 2: Windows 10 1703 x64 with X2Go Client 4.1.0.0-2017.03.11

1 0

Bug#1179: Cannot select Display # from Session Preferences
by Mike DePaulo 24 May '17

24 May '17

Package: x2goclient Version: 4.1.0.0 Severity: normal Tags: +build-win32 In X2Go Client for Windows, from the main menu, I can click on the the Display dropdown and select "Display 1". However, from Session Preferences, I cannot select it. The similar options such as "fullscreen" and "maximum available" are not the same behavior. (For example, "maximum available" exhibits bug #618, and "fullscreen" exhibits bug #1178, but "Display 1" exhibits neither of those.) Note: This is a single monitor client.

1 0

Bug#1178: X2Go Client for Windows in Fullscreen mode has VcXsrv fail with "InitOutput - Couldn't add screen 0"
by Mike DePaulo 24 May '17

24 May '17

Package: x2goclient Version: 4.1.0.0 Severity: normal Tags: +build-win32 When I attempt to launch a Fullscreen session of X2Go Client for Windows, I get an error window from VcXsrv (which fails to start): A fatal error has occuered and VcXsrv will now exit. InitOutput - Couldn't add screen 0 ... <It references the attached log file> Vendor: The X2Go and Arctica Projects Release: 1.17.0.0 ... XWin was started with the following command-line: vcxsrv -fullscreen -notrayicon -clipboard :0 Client: Windows 7 x64 SP1 with 2560x1440 resolution and the scaling set to "Larger - 150%" server: CentOS 7.3 x64 with KDE

1 0

Bug#1177: Sound does not work from EL6 clients with both pulse cookies
by Mike DePaulo 24 May '17

24 May '17

Package: x2goclient Version: 4.1.0.1 PulseAudio Sound fails to work when the following conditions are met: 1. The client is running RHEL 6/CentOS 6/etc 2. The client has both ~/.pulse-cookie ~/.config/pulse/cookie . For example, when the home directory is an NFS export mounted by both EL6 and EL7 systems. Running commands like `pactl list` on the X2Go server yields "Connection failure: Access denied". This is because the X2Go client system is using ~/.pulse-cookie with its PulseAudio server, but X2Go Client copied over ~/.config/pulse/cookie and is having the X2Go server system use it with its PulseAudio client libraries. This can be worked around by symlinking .pulse-cookie to .config/pulse/cookie .

1 0

Bug#1167: More details
by Petronic, Mark 20 May '17

20 May '17

We are running Windows 7 using VmWare Virtual Desktop (VDI). So, my x2go client runs on that Windows desktop. The crash is actually happening in vcxsrv.ex and I was able to obtain the following additional information: (1) The VDI admins updated some VDI runtimes on our VDI desktop instances to VMWare version 6 around the time we started to experience this crash (2) Here is a more detailed dump of some debug information I found: Problem signature: Problem Event Name: APPCRASH Application Name: vcxsrv.exe Application Version: 1.17.0.0 Application Timestamp: 55b5056a Fault Module Name: vm3dum.dll Fault Module Version: 8.15.1.46 Fault Module Timestamp: 57112640 Exception Code: 40000015 Exception Offset: 00026b27 OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 Additional Information 1: f5d8 Additional Information 2: f5d85880320133c2803765541f044878 Additional Information 3: 4651 Additional Information 4: 4651b47fc82bdc83b534297b987ba7e7

2 2

Bug#1176: Replace netstat with ss
by Orion Poplawski 17 May '17

17 May '17

Package: x2goserver Version: 4.1.0.0 netstat is depracated by ss. We should replace it in x2goresume-session, especially since we already use ss in x2gostartagent. -- Orion Poplawski Technical Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

1 0

Xinerama buggy?
by Ulrich Sibiller 15 May '17

15 May '17

Hi, in x2goclient's ONMainWindow::slotConfigXinerama you can find the following code that calculates the values for xinerama.conf. We see a race condition here where sometimes (well, quite often) this leads to negative x/y coordinates in xinerama.conf (size is ok) for new sessions when run from the thinclient setup. The code below contains annotations by me in [] with the variables' values that lead to the wrong xinerama.conf. I believe x2goclient sometimes catches the nxagent window too early before it is resized accordingly (maybe the window manager is too slow) thus getting a window of size 1x1 in the center of the screen (line 12): 1 void ONMainWindow::slotConfigXinerama() 2 { 3 QRect newGeometry=proxyWinGeometry(); [1x1@511,393] 4 if (newGeometry.isNull()) 5 { 6 x2goWarningf(7)<< tr("Error getting window geometry. (Did you close the window?)"); 7 xineramaTimer->stop(); 8 return; 9 } 10 if (newGeometry==lastDisplayGeometry) 11 return; 12 lastDisplayGeometry=newGeometry; [1x1@511,393] 13 QString geoStr = 14 "(x: " + QString("%1").arg(lastDisplayGeometry.x()) + 15 ", y: "+ QString("%1").arg(lastDisplayGeometry.y()) + 16 ", w: "+ QString("%1").arg(lastDisplayGeometry.width()) + 17 ", h: "+ QString("%1").arg(lastDisplayGeometry.height()); 18 x2goDebug<<"New proxy geometry: " + geoStr; 19 QDesktopWidget* root=QApplication::desktop(); 20 QList<QRect> newXineramaScreens; 21 for (int i=0; i< root->numScreens(); ++i) 22 { 23 QRect intersection; 24 if (resumingSession.fullscreen) 25 intersection=root->screenGeometry(i); [1024x768@0,0] 26 else 27 intersection=root->screenGeometry(i).intersected(lastDisplayGeometry); [ not executed ] 28 if (!intersection.isNull()) 29 { 30 // x2goDebug<<"intersected with "<<i<<": "<<intersection<<endl; 31 intersection.moveLeft(intersection.x()-lastDisplayGeometry.x()); [1024x768@-511,0] <- [0]-[511] 32 intersection.moveTop(intersection.y()-lastDisplayGeometry.y()); [1024x768@-511,-393] <- [0]-[393] 33 // x2goDebug<<"xinerama screen: "<<intersection<<endl; 34 newXineramaScreens<<intersection; 35 } 36 } 37 if (xineramaScreens != newXineramaScreens) 38 { 39 xineramaScreens=newXineramaScreens; 40 // x2goDebug<<"xinerama screen changed, new screens: "<<xineramaScreens<<endl; 41 xineramaTimer->stop(); 42 QStringList screens; 43 foreach (QRect disp, xineramaScreens) 44 screens<<QString::number(disp.x())+" "+QString::number(disp.y())+" "+QString::number(disp.width())+ 45 " "+QString::number(disp.height()); ["-511 -393 1024 768"] 46 QString cmd="export DISPLAY=:"+resumingSession.display+" ;printf %b '\\''"+screens.join("\\n")+"'\\'' > $HOME/.x2go/C-"+ 47 resumingSession.sessionId+"/xinerama.conf"; 48 sshConnection->executeCommand(cmd, this, SLOT(slotXineramaConfigured())); 49 } 50 } I am not really sure about the intentions behind this code. It looks to me that the if block (lines 28-35} should not run for the fullscreen case. Can anyone confirm this? Uli

1 0

Bug#1016: X2Go issue (in src:python-x2go) has been marked as closed
by X2Go Release Manager 15 May '17

15 May '17

close #1016 thanks Hello, we are very hopeful that X2Go issue #1016 reported by you has been resolved in the new release (0.5.0.5) of the X2Go source project »src:python-x2go«. You can view the complete changelog entry of src:python-x2go (0.5.0.5) below, and you can use the following link to view all the code changes between this and the last release of src:python-x2go. http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=64c77967e7ae4e… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:python-x2go. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:python-x2go Version: 0.5.0.5-0x2go1 Status: RELEASE Date: Mon, 15 May 2017 16:38:16 +0200 Fixes: 1016 Changes: python-x2go (0.5.0.5-0x2go1) RELEASED; urgency=low . [ Mike Gabriel ] * New upstream version (0.5.0.5): - documentation: Fix wording in docstring. - Don't blindly release gevent locks. We need to check if a semaphore is locked for some code paths and only then release it. (Fixes: #1016). . [ Mihai Moldovan ] * New upstream version (0.5.0.5): - x2go/__init__.py: update mailing list address. * debian/control: - Maintainer change in package: X2Go Developers <x2go-dev(a)lists.x2go.org>. - Uploaders: add myself. Also, force a rebuild due to the changed versioning.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev