x2go-dev

x2go-dev@lists.x2go.org

5403 discussions

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

Bug#1222: Timeout of about 30s to start the x2go session
by Bruno CAPELETO 04 Oct '17

04 Oct '17

Package: <x2goserver> Version: <4.1.0.0-0x2go1.2~git20170806.1410+9.heuler.1> # uname -a Linux mtcie1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux # cat /etc/issue Debian GNU/Linux 9 \n \l When connecting to this x2go server - linux client and/or Windows client, I tested both - the session takes about 30s to start. I checked the /var/log/auth.log : the ssh connexion is pretty fast (1-2s) I checked the x2go session.log : it is finished about 30s later What happens during these 30s I do not understand. I have other installations on Debian 8, this does not take so long.

1 0

Bug#1018: The problem still exists
by Chessplayer 28 Sep '17

28 Sep '17

Hi guys, unfortunately, there has been no response to this bug report for over a year and also no answer to this question on the Ubuntu forum: https://forum.ubuntuusers.de/topic/x2go-und-path-variable/ The problem still remains ... Do you plan on doing something about it? Cheers, chessplayer

1 0

X2Go Developer Meeting 2017-09-28 20:30 CEST / 02:30pm EDT
by Stefan Baur 27 Sep '17

27 Sep '17

Dear $ALL, As you probably know from the Wiki and from previous announcements on the lists, X2Go: The Gathering 2017 took place last weekend. One of the things decided/agreed on at this event was that we should have Developer Meetings more regularly. The plan is to aim for one DevMeeting per quarter, though obviously additional ones can be set up if the need arises. The next DevMeeting is scheduled for tomorrow, 2017-09-28, 20:30 CEST / 02:30 EDT. We will gather in #x2go on irc.freenode.net and discuss the required X2GoServer code updates in preparation of the upcoming release, which we intend to finish by early December 2017. Future DevMeetings may take a "hybrid" form, with some people gathering in a hackerspace (or hackerspaces), and others joining in via IRC. Kind Regards, Stefan Baur X2Go Project/Community Manager -- 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#1172: Fwd: Modifier Keys not working as expected
by Ulrich Sibiller 26 Sep '17

26 Sep '17

On Tue, Sep 26, 2017 at 1:57 PM, Stefan Baur <X2Go-ML-1(a)baur-itcs.de> wrote: > Am 26.09.2017 um 12:20 schrieb Ulrich Sibiller: > >>> A certain application requires the following keypresses: >> >> Is the spplication's name secret? > > No, but closed-source/commercial/proprietary. > > >>> - Hold down ctrl, shift and alt >>> - while holding them down, press the space bar >>> - let go of shift and space bar, keep holding down ctrl and alt >> >> leaving you with ctrl-alt > > In theory, yes. But somehow the shift and space bar being pressed and > released first tell it to "keep" the keypresses to itself, rather than > sending them and the function key on to the X Server. No, it's the other way round. The X server gets the keypresses and passes them on to the client(s). This application probably instructs the xserver to send these keys only to the app and not to anyone else (and neither interpret them itself). https://tronche.com/gui/x/xlib/input/XGrabKeyboard.html states this: The XGrabKeyboard() function actively grabs control of the keyboard and generates FocusIn and FocusOut events. Further key events are reported only to the grabbing client. [...] If the keyboard_mode argument is GrabModeAsync, keyboard event processing continues as usual. If the keyboard is currently frozen by this client, then processing of keyboard events is resumed. If the keyboard_mode argument is GrabModeSync , the state of the keyboard (as seen by client applications) appears to freeze, and the X server generates no further keyboard events until the grabbing client issues a releasing XAllowEvents() call or until the keyboard grab is released. Actual keyboard changes are not lost while the keyboard is frozen; they are simply queued in the server for later processing. >> But for analysis we'd need the application to see what is doing. > > They offer a time-limited trial version [0], but IIRC, you still need to > register somewhere with your E-Mail address (and they'll send you promo > E-Mails during the trial phase, and possibly even afterwards). > > >> For the records: I think it is nx-libs so we should open an issue >> there. But I am not sure if we will be able to fix that at all. > > As I said, feel free to do so - you're way more knowledgeable about the > code involved than I am. I can do that eventually. Uli

1 0

Bug#1220: Modifier Keys not working as expected
by Stefan Baur 26 Sep '17

26 Sep '17

package: x2goclient (devs: feel free to reassign this to nx-libs/arctica, if the cause is not in X2GoClient) A certain application requires the following keypresses: - Hold down ctrl, shift and alt - while holding them down, press the space bar - let go of shift and space bar, keep holding down ctrl and alt - with ctrl and alt pressed, press a function key (F1-F6) - let go of all keys This works when the application is run on :0 - the "ctrl-alt-Fx" is not passed down to X, so no switch to tty1-tty6 occurs, which is the intended and expected behavior. However, with the application running in an X2Go session, the same sequence of keys will trigger a switch to tty1-tty6 on the local client. -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 2

Bug#1208: Messed up session when resuming from Published Apps mode to Fullscreen desktop mode in thinclient mode
by Walid MOGHRABI 26 Sep '17

26 Sep '17

Package: x2gothinclient Version: 4.1.1.0-0~1634~ubuntu16.04.1 Let's say you suspended a session in "Published Apps" mode from a local desktop (might be Linux or Windows, it doesn't matter) then try to resume it from a TCE running the client in thinclient mode. This will work, you can resume the session but the display is completely broken : no desktop, no decorations, corrupted display and no widget to logoff so you're stuck there unless someone kills your session from the server. It would be better to simply block the ability to resume a Published Apps session in a mode where it just can't be done such as the thinclient mode. 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

3 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev