x2go-dev

x2go-dev@lists.x2go.org

1 participants
5403 discussions

Bug#618: KDE panel and LXDE panel are hidden after login to x2go session
by Aki Ketolainen 29 May '17

29 May '17

Package: x2goagent Version: 2:3.5.0.27-0~446~ubuntu14.04.1 Package: x2goserver Version: 4.0.1.15-0~847~ubuntu14.04.1 Package: x2goserver-extensions Version: 4.0.1.15-0~847~ubuntu14.04.1 Package: x2goclient Version: 4.0.2.1+hotfix1+build4 Server = Ubuntu 14.04.1 LTS (x86) Client = Windows 8.1 (x86_64) After logging into x2go Server, I see either KDE or LXDE start up, as configured. Start up finishes but the panel in either KDE or LXDE is not shown. I press Alt+F2 to open the 'Run' application and start xterm. I run 'xrandr -s 1280x720', the x2go/X11 window size changes OK and the menu in either KDE or LXDE shows up automatically. I saw that someone had ran into this bug in 2012: http://readlist.com/lists/gentoo.org/gentoo-user/33/169010.html but there was just a temporary resolution to the problem.

3 4

Bug#618: Bug#618: Bug#618: nx-libs 3.6 beta fixes this
by Mike Gabriel 29 May '17

29 May '17

Control: fixed -1 3.5.99.7 On Mo 29 Mai 2017 10:49:28 CEST, Mike Gabriel wrote: > Control: tags -1 fixed 3.5.99.7 The above control command was non-sense... Fixing it with this mail. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

1 0

Bug#618: nx-libs 3.6 beta fixes this
by Mike DePaulo 29 May '17

29 May '17

FYI, this problem goes away when the server is upgraded to nx-libs 3.6 beta. Tested with nx-libs 3.5.99.4 & 3.5.99.7 on RHEL 7.3. https://copr.fedorainfracloud.org/coprs/mikedep333/nx-libs-3.6/

2 2

Bug#1182: nxagent 3.6 and KDE4 causes X2Go Client for Windows's session window to "jump" up and down
by Mike DePaulo 29 May '17

29 May '17

Package: x2goclient Version: 4.1.0.0 Note: It is unclear whether this is a bug in nx-libs or x2goclient/VcXsrv Note: This bug does not occur with nxagent 3.5 (& x2goserver 4.0.1.20-1.el7 from EPEL) Note: This bug does not occur for Linux clients. Steps: 1. Start a KDE4 session in windowed mode. 2. Maximize the session. 3. Observe that the session window "jumps" up and down by tens of pixels. This happens repeatedly and very quickly. It has the appearance of it flickering almost. It makes it largely unusable. Note: This seems to go away on its own after seconds on my Windows 10 client, but it lasted indefinitely on my Windows 7 client. Server: CentOS 7.3 with KDE4 & x2goserver 4.1.0.0 nightly & nx-libs 3.5.99.7 (from copr repo mikedep333/nx-libs-3.6) Client 1: Windows 7 x64 SP1 with X2Go Client 4.1.0.0-2017.03.11 Client 2 Configuration 1: Windows 10 1703 x64 with X2Go Client 4.1.0.0-2017.03.11 (This has nx-libs 3.5.0.32) Client 2 Configuration 2: Windows 10 1703 x64 with X2Go Client 4.1.0.0-2017.03.11 & VcXsrv 1.19.2.0 (I replaced the VcXsrv subfolder) (This has nx-libs 3.5.0.32)

3 4

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev