x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

NIS user from a Mac disconnects upon login with Fedora 26 nightly build
by Robert Kudyba 24 Oct '17

24 Oct '17

We have a Mac user with a NIS account, and X2Go just quits after authenticating. I’ve restarted DBUS, systemd-logind, x2goserver, and deleted the user .x2go directory, X2Go just goes black and disappears. I posted the client and server debug logs to http://lists.x2go.org/pipermail/x2go-user/2017-October/004591.html and we are using the nightly builds: x2goserver-4.1.0.0-0.0x2go1.0.git20171015.1421.heuler.fc26.x86_64 Sorry if cross-posting is discouraged but noone replied on the user list and it's been several days. Also when enabling the nightly builds is it as simple as changing the flag in the x2go.repo file as such? [x2go-nightly-fedora] name=Upstream X2Go Fedora Packages (Nightly Builds) baseurl=http://packages.x2go.org/fedora/$releasever/heuler/$basearch gpgcheck=1 gpgkey=http://packages.x2go.org/pub.key enabled=1 protect=0 [x2go-extras-fedora] is also enabled. [x2go-release-fedora] is disabled.

1 0

Bug#1135: MySQL session backend
by Walid MOGHRABI 20 Oct '17

20 Oct '17

I forgot the modified /etc/x2go/x2gosql/sql file ... Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1135: MySQL session backend (fixed version)
by Walid MOGHRABI 20 Oct '17

20 Oct '17

package: x2goserver priority: wishlist tags: patch This is a proposal patch for a MySQL session storage database backend for X2Go Server. I did this simply because : 1) I'm not used to PostgreSQL and much more skilled with MySQL 2) I do believe MySQL is pretty common on Linux and is widely spread so I guess this can be useful for many other people willing to build a strong TCE setup and not willing to dig into PostgreSQL 3) I find it a lot easier to build a multi-master replication scenario with MySQL than with PostgreSQL (but as I said, I'm much more skilled wih MySQL) This backend is tightly inspired by the PostgreSQL backend and work exactly the same so this is a drop in replacement for it, it's running in my POC for months now and it has been proven very stable. Feel free to test by yourself and report errors. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1227: Close button in thinclient mode
by Walid MOGHRABI 20 Oct '17

20 Oct '17

package: x2goclient priority: wishlist tags: patch This is a proposal patch for a close button in addition to the current halt button in thinclient mode. Context : When logged in (right after the credentials prompt, in the client view where all available session slots are listed), if you entered by mistake and just want to get back to the credential form, there is o way to "logout". Only possibilities are : * halt button but it will shutdown the computer * log to a remote X2Go session then logout which is a annoying process. The patch is not complete, currently it adds the button but the same way as for halt button and it simply close the client which is slow instead of just get back to the credential form which would be smoother and faster. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1224: x2go desktop starts with incorrect resolution on Ubuntu 16.04
by feng zhang 12 Oct '17

12 Oct '17

Package: x2goserver Version: 4.0.1.20-0 Server: Ubuntu 16.04 64-bit Client: Linux Mint 18.2 Mate 64-bit The server has Mate desktop and x2gomatebindings installed. The client machine has two monitors. When I configure the x2goclient to "Use whole display" of "Display #2," I would get a desktop of 800x600 upon logging in. If I suspend the session, and then resume it, I would get a desktop that correctly fits the entire monitor (1680x1050.) When connecting to another server that runs Ubuntu 14.04, this problem doesn't occur. The "Fullscreen" mode works correctly on both servers. Thanks, feng -- ------------------- Feng Zhang, Ph.D. LumArray, Inc. 15 Ward Street Somerville, MA 02143 (617)996-5833

2 1

Processed: your mail
by owner＠bugs.x2go.org 12 Oct '17

12 Oct '17

Processing commands for control(a)bugs.x2go.org: > fixed 1100 4.1.1.0 Bug #1100 [x2goclient] xterm's shell started from x2goclient has wrong PATH There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture '' Unable to make a source version for version '4.1.1.0' Marked as fixed in versions 4.1.1.0. > reassign 1018 x2goclient 4.0.5.1 Bug #1018 [x2goserver] PATH not set correctly Bug reassigned from package 'x2goserver' to 'x2goclient'. No longer marked as found in versions 4.0.1.19-0. Ignoring request to alter fixed versions of bug #1018 to the same values previously set Bug #1018 [x2goclient] PATH not set correctly There is no source info for the package 'x2goclient' at version '4.0.5.1' with architecture '' Unable to make a source version for version '4.0.5.1' Marked as found in versions 4.0.5.1. > reassign 1199 x2goclient 4.0.5.1 Bug #1199 [x2goserver] PATH environment variable SET issue Bug reassigned from package 'x2goserver' to 'x2goclient'. No longer marked as found in versions 4.0.1.20-1. Ignoring request to alter fixed versions of bug #1199 to the same values previously set Bug #1199 [x2goclient] PATH environment variable SET issue There is no source info for the package 'x2goclient' at version '4.0.5.1' with architecture '' Unable to make a source version for version '4.0.5.1' Marked as found in versions 4.0.5.1. > forcemerge 1018 1100 Bug #1018 [x2goclient] PATH not set correctly Bug #1018 [x2goclient] PATH not set correctly There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture '' Unable to make a source version for version '4.1.0.1' There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture '' Unable to make a source version for version '4.1.1.0' Marked as fixed in versions 4.1.1.0 and 4.1.0.1. Added tag(s) pending. Bug #1100 [x2goclient] xterm's shell started from x2goclient has wrong PATH Merged 1018 1100 > forcemerge 1199 1100 Bug #1199 [x2goclient] PATH environment variable SET issue Bug #1199 [x2goclient] PATH environment variable SET issue There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture '' Unable to make a source version for version '4.1.0.1' There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture '' Unable to make a source version for version '4.1.1.0' Marked as fixed in versions 4.1.1.0 and 4.1.0.1. Added tag(s) pending. Bug #1018 [x2goclient] PATH not set correctly Bug #1100 [x2goclient] xterm's shell started from x2goclient has wrong PATH Merged 1018 1100 1199 > thanks Stopping processing here. Please contact me if you need assistance. -- 1018: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1018 1100: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1100 1199: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1199 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#740: Ship a default, small-footprint, F/LOSS PDF viewer with x2goclient
by Stefan Baur 11 Oct '17

11 Oct '17

Alex and I had a look at this bug while @ X2Go: The Gathering 2017. We currently have a drop-down list of printers to choose from, and the option to specify a custom print command instead (using a checkbox and a text field). The idea would be: - SumatraPDF becomes the new default PDF viewer for X2GoClient for Windows and gets bundled with it, just like VcXsrv. - You will be able to de-select it during X2GoClient installation, if you prefer using your own PDF viewer and want to save a few megabytes of storage. - There will be the following options using SumatraPDF "behind the scenes" in the print dialog: - An option to always print to the system default printer - The current "choose a printer" dialog, which will set a default for X2GoClient only - An option to always prompt the user to select a printer when a print job is being sent. - The option to specify a custom print command in the print dialog will remain. It will default to a SumatraPDF call with sample parameters on Windows systems. - The option to specify a viewer command for PDFs in the "Show as PDF" dialog will remain, and will default to SumatraPDF on Windows systems. This feature request ist currently awaiting funding. It is expected to take no longer than 8 hours to implement, once funded. -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

2 1

Bug#1221: Server Side PulseAudio Server and compression of audio data
by Oleksandr Shneyder 11 Oct '17

11 Oct '17

Package: x2goserver Severity: wishlist currently X2Go Client starts PulseAudio on the client side to play sound. The PA clients on the server sending data through SSH tunnel to PA server on X2Go Client. This scenario has two big disadvantages: 1. We need to provide PA Server with X2Go Client on Windows and Mac OS. 2. PA clients sending data in raw format (uncompressed). This costs a lot of bandwidth and make playing sound on slow Internet connections almost impossible. The idea is to use mediastreamer2 + ortp libraries to deal with data compression and audio hardware on the client side: http://www.linphone.org/technical-corner/mediastreamer2/overview we'll also need to create a PA backend for mediatreamer2 on the server side. best regards Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder(a)phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Harzstr. 4 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------

2 1

Strategy for introducing Python3 ports of PyHoca and X2Go Broker
by Mike Gabriel 09 Oct '17

09 Oct '17

Hi, as some of you might already know, I started porting the X2Go Session Broker and Python X2Go + PyHoca-CLI to Python3 during the X2Go Gathering 2017. (Unfortunately, Pyhoca-GUI is not yet portable, as python-wxgtk is not yet available a python3-wxgtk, at least not on my development system, which is Debian). The question now is, how to start the transition. The code may still be flawed here and there, so this requires some thorough phase of testing. First, the idea is to have the Python3 ports on the master branches in Git, while keeping the Python2 code maintained on several release branches in Git: Python X2Go: release/0.5.0.x https://code.x2go.org/gitweb?p=python-x2go.git;a=shortlog;h=refs/heads/rele… PyHoca-CLI: release/0.5.0.x https://code.x2go.org/gitweb?p=pyhoca-cli.git;a=shortlog;h=refs/heads/relea… X2Go Session Broker: release/0.0.3.x https://code.x2go.org/gitweb?p=x2gobroker.git;a=shortlog;h=refs/heads/relea… The code has already been pushed to those branches, however, the builds fail on various old distros. Mostly, due to missing Python3 dependencies (e.g. python3-gevent is missing in Debian jessie, but a requirement for python3-x2go). Some builds also fail due to the API documentation system being used (epydoc). This is work in progress and will be fixed by the end of this week. The idea now--build-wise--is to build the Python3 ports for a considerable amount of time _only_ against those distro versions, that are not yet released--thus in testing phase--themselves, that is: Debian testing Debian unstable Fedora rawhide openSUSE Factory (I don't see builds for Factory on jenkins.x2go.org, though) All released distros (Debian (old)stable, Centos 6+7, Fedora XY, etc.) will receive nightly built packages from the above mentioned release branches. Benefits are: - master branches and release branches can be tested via nightly builds - no dodgy backporting and lack of maintenance for python dependencies (see: http://packages.x2go.org/debian/pool/main/p/) - stable distro releases will not receive flawed code (the Python3 port cannot be considered as stable at all, I continuously find more issues popping up while testing) Disadvantages: - nightly builds don't build the same Git branches anymore. What you find in the nightly built package repo (aka heuler) depends on your Linux distro and version Comments? Requests for feedback! Thanks! 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#1223: SSH daemon could not be started
by JONATHAN EPPS 06 Oct '17

06 Oct '17

Package: Is it possible that I may not have downloaded a package? How do I know what package I have and where can I find that information? Version: 4.1.0.0 You have enabled Remote Printing or File Sharing. These features require a running and functioning SSH server on your computer. Printing and File Sharing will be disabled for this session. Normally, this should not happen as X2Go Client for Windows ships its own internal SSH server. If you see this message, please report a bug on: https://wiki.x2go.org/doku.php/wiki:bugs Disabling Remote Printing or File Sharing support in the session settings will get rid of this message. My machine: Windows 10 Home Edition, Version 1607 with a 64-bit operating system, x64-based processor My version of X2GoClient: v 4.1.0.0

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