x2go-user

x2go-user@lists.x2go.org

2 participants
2322 discussions

Ubuntu 17.04
by Robert Dinse 25 Apr '17

25 Apr '17

On a machine that x2go was not working, I did a fresh install of Ubuntu Mate 17.04 then only did upgrades. Then I installed x2goserver, x2goserver-xsession, and x2goclient. It worked except that it gave me an 800x600 screen unless I manually reset it using xrandr -s 1680x1050 from the command line. I then installed arctica project Sunweaver's Net nx-libraries, and now it exploded when it tried to connect. I backed out those libs and it worked again. So something has changeed, yet, on two other machines I have arctica project's libs installed and all is well. The only difference is that those machines started out life as 14.04 and were upgraded in place to 17.04, as opposed to being fresh installs. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

x2go display not opening on windows 10
by Gladia Hotan 24 Apr '17

24 Apr '17

Hi, After a recent windows 10 update, my x2go window no longer opens. The taskbar icon appears and the program is shown as 'running' in task manager, but there is no display window. Any ideas how to fix this? Thanks and best regards, Gladia

1 0

usb fingerprint
by Olaf St. 24 Apr '17

24 Apr '17

Hi! Is there any solution to use usb fingerprint sensor to log-in/load sessions with x2go tce? ⁣Bye, Olaf Gesendet mit TypeApp

1 0

x2goserver can support mutliple clients?
by Randell Palmer 19 Apr '17

19 Apr '17

I have setup a x2goserver and 2 x2goclients : client1 & client 2 Either of the clients will work when it is the only client receiving service from the x2goserver. I can connect one of the x2goclients, client1, to the x2goserver and it will bring up xfce4 as requested and can play music etc. However when I try to start client2 I get the menu which has 3 options. Suspend Terminate New If I select New then the X2GO screen briefly appears and then it returns to the menu. If I select terminate, it kills the session on client1 and then I can select New and client2 will display XFCE4. Is this expected behavior? All 3 are running freshly installed Arch linux. Thank you

4 7

Windows x2go client displays at incorrect resolution
by Davis, Jean-Paul 18 Apr '17

18 Apr '17

I'm hoping that someone out there with more experience will be able to solve this problem! Server = RHEL 7, running local GNOME-3 session at native 3840x2160 (dpi 149) of attached 4K display Installed Packages: x2goagent.x86_64 3.5.0.32-3.el7 @epel x2goclient.x86_64 4.1.0.0-1.el7 @epel-rhel-x86_64-workstation-7 x2goserver.x86_64 4.0.1.20-1.el7 @epel x2goserver-xsession.x86_64 4.0.1.20-1.el7 @epel Settings: /etc/x2go/x2go-agent.options - commented out X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension XFIXES" /etc/x2go/Xresources - set Xft.dpi: 192 Everything else left at defaults Client = Windows 10, x2go client v4.1.0.0, local native display 2560x1440 (dpi 192) Settings: Session Type = MATE (automatically changes to "Custom desktop" with command "MATE") Display = Fullscreen Set display DPI = 192 The session starts just fine, filling the screen with the MATE desktop, except that the display resolution is incorrect... with following information obtained inside a MATE terminal: jpdavis: xdpyinfo | grep dots resolution: 192x193 dots per inch jpdavis: ps -waux | grep $DISPLAY | grep x2goagent jpdavis 28204 0.2 0.3 217268 57696 ? S 10:05 0:08 /usr/lib64/nx/../x2go/bin/x2goagent -nolisten tcp -nolisten tcp -dpi 192 -D -auth /home/jpdavis/.Xauthority -name X2GO-jpdavis-50-1491062721_stDMATE_dp32 :50 jpdavis: xrandr --prop xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 240, current 1280 x 720, maximum 1920 x 1200 default connected 1280x720+0+0 0mm x 0mm Thus the actual dpi being used by the display is 192*1280/2560 = 96, not the 192 sent to x2goagent and reported by xdpyinfo. attempting to change the resolution from inside the session... xrandr --size 1920x1200 works but keeps same actual dpi of 96 (so desktop is larger than my screen) MATE Settings->Hardware->Displays returns error "RANDR extension is too old (must be at least 1.3)" xrandr --version returns xrandr program version 1.4.3 Server reports RandR version 1.2 I get the same behavior if I try sessions with KDE or XFCE instead of MATE. Since the maximum resolution reported by xrandr corresponds to dpi of 192*1920/2560=144 x 192*1200/1440=160, I wondered if it had something to do with the local X session on the server which is at 149 dpi; closing that session, however, makes no difference. Could it be something about the X server that is running on the x2go server? (It is running but with no sessions, just the login greeter). The Windows client generates the following in the file .x2go\<session>\sessions: Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Auth: WARNING! Failed to read data from the X auth command. Auth: WARNING! Generating a fake cookie for X authentication. Loop: WARNING! Could not retrieve the X server authentication cookie. Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... ... and the following in the file .x2go\<session>\options: nx/nx,root=/cygdrive/C/Users/jpdavis/X2GO~1,connect=localhost,cookie=6f9207806bc4e3206aa5df26759c77bc,port=60732,errors=/cygdrive/C/Users/jpdavis/X2GO~1/S-JPDA~1/sessions:50 Where could it be getting a session type of 'unix-kde-depth_32' when I've set it to use a MATE session? And where exactly do I find the /cygdrive/C/Users/jpdavis/X2GO~1 directory on my Windows machine? I can't find any files where x2go client saves program preferences or session preferences. Under the client settings, I changed to "use custom X server", pointed to the VcXsrv.exe file that comes with x2go, added "-dpi 192" to the command-line options for all cases, and restarted x2go. This had no effect. I also tried using the XMing X server with the same options, this also had no effect. More interesting information... If I simply Putty ssh to the server and run xrandr I get "Can't open display." If I enable X11 forwarding in Putty but don't start a local X server on the Windows machine, then xrandr returns slightly more information: "Can't open display 134.253.62.153:10.0." If I do this again but first start VcXsrv with the same command-line options as I've set in x2go ("C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" -fullscreen -notrayicon -clipboard -dpi 192) then xrandr returns "Screen 0: minimum 0 x 0, current 1280 x 720, maximum 4096 x 4096" (and xdpyinfo still says "192x193 dots per inch"). If I also add the command-line options "-screen 0 2056x1440", I get that resolution but much larger than my real display, and text is even larger. Finally, I tried using Putty X11 forwarding with XMing, with XMing options set via it's XLaunch executable. With XMing set to fullscreen and no additional options passed, xdpyinfo says "75x75 dots per inch" and xrandr returns "Screen 0: minimum 1280 x 720, current 1280 x 720, maximum 1280 x 72." Same result with XMing set to multiple windows. In this mode, graphical applications started from inside Putty actually don't look bad (normal text size). Adding command line option "-dpi 192" to XMing makes xdpyinfo return "192x193 dots per inch" but xrandr output remains the same, and the resulting graphical application text is way too large. Using XMing with Putty and X11 forwarding to start mate-session has the same issue, so I guess this is not actually an x2go problem. I'm still posting here in case someone can help, maybe I'll also look for user mail lists relevant to X in general, or VcXsrv/XMing. So what am I missing? Where is it getting the dpi=96 that the display is actually using? The 96 value makes the session fairly useless, as all display elements are huge compared to the screen. I had this working not that long ago, but I wouldn't be able to confirm exactly what changes have been made in the interim because I don't recall exactly _when_ it was working. Jean-Paul Davis

2 3

Running without window/desktop manager
by Marat Khalili 12 Apr '17

12 Apr '17

Dear all, I'm new to X2Go having used FreeNX previously. I've installed x2goserver on Ubuntu 16.04 server from ppa:x2go/stable, and can start published applications successfully. However, I didn't install any window or desktop manager, since I don't think my clients will need it. Neither did I install any bindings. I wonder, what features do I lose this way? Particularly, neither local printing nor shared folders seem to work (tested from Windows and Ubuntu 14.04 stock client), can this be related, or is it a separate problem? Directory ~/media/disk exists, but it is empty; and only "Print to File" is available in remote Firefox. If window/desktop manager is needed, which should I install to handle just this problem? Do I need bindings package too? (I'd prefer not to have unnecessary packages on my server to avoid frequent security updates.) -- -- With Best Regards, Marat Khalili

2 2

Sponsorship of X2Go macOS Client Development and of X2Go Linux on POWER Development
by Stefan Baur 07 Apr '17

07 Apr '17

Hi everyone, as previously announced, CFD.direct has decided to sponsor our macOS Client Development, and XCLOUD.me, has jumped right in and offered us a special rebate, so we can run two of their smallest instances for the price of one medium instance. This means that will be able to offer automated X2GoClient for macOS builds both for macOS 10.10 (these should work on 10.9 and 10.8 as well) as well as for macOS 10.12. The machines have been provisioned today, and Mihai will be setting them up over the course of the next few days. Once he's done with that, we'll move on to supporting the POWER platform directly again (at present, some distributions grab our source and turn it into packages for their POWER flavor, but there's no official X2Go repository where you could get stable or nightly builds directly from us). IBM and the Oregon State University's Open Source Lab have teamed up and are providing us with four POWER8 virtual machines (with the option to add more, should the need arise), manageable via an OpenStack WebGUI. Unlike the previous POWER8 virtual machine that we had, these new servers are going to be available for us for the foreseeable future. We intend to run at least two (one for Big-Endian, the other for Little-Endian) of those machines as Jenkins Build Slaves, just as the virtual macOS machines, so we will soon be able to provide automated builds for POWER. The other two we currently intend to run as demo servers and for testing and bugsquashing, though we might repurpose them as Jenkins Build Slaves if it turns out that we need one per Endianess *and* packaging system (DEB vs. RPM). There's one bug that's cropped up on POWER8 LE only, and we're already curious to learn what's causing it, so we're glad we finally have access to a test environment again. Here is a quick overview over the sponsors mentioned above: CFD Direct <https://cfd.direct> are the primary developers of OpenFOAM <https://openfoam.org>, the free, open source software for computational fluid dynamics. XCLOUD.me <https://xcloud.me/> is a hosting company that specializes in providing virtual macOS cloud instances - all 100% legal, as the virtual machines run on top of real Apple hardware. IBM are the original developers of the POWER systems used in midrange computing. You can learn more about the Linux on POWER ecosystem here: <http://www-03.ibm.com/systems/power/software/linux/> Oregon State University's Open Source Lab (OSU/OSL) is a nonprofit organization working for the advancement of open source technologies. They offer various means of support to open source projects, one of them being free hosting on both Intel and POWER servers. To find out more about them, please visit their web site at <http://osuosl.org/> 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

Fedora 25
by Robert Dinse 06 Apr '17

06 Apr '17

Something broke in Fedora 25 and now the only window manager I can get to work over x2go is icewm, mate will no longer start, kde will no longer start. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

3 2

Re: [X2Go-User] Windows x2go client displays at incorrect resolution
by Davis, Jean-Paul 04 Apr '17

04 Apr '17

> > Session Type = MATE (automatically changes to "Custom desktop" with > > command "MATE") Display = Fullscreen Set display DPI = 192 > > > > The session starts just fine, filling the screen with the MATE > > desktop, except that the display resolution is incorrect... with > > following information obtained inside a MATE terminal: > > > > jpdavis: xdpyinfo | grep dots > > > > resolution: 192x193 dots per inch > > > > jpdavis: ps -waux | grep $DISPLAY | grep x2goagent > > > > jpdavis 28204 0.2 0.3 217268 57696 ? S 10:05 0:08 > > /usr/lib64/nx/../x2go/bin/x2goagent -nolisten tcp -nolisten tcp -dpi > > 192 -D -auth /home/jpdavis/.Xauthority -name > > X2GO-jpdavis-50-1491062721_stDMATE_dp32 :50 > > > > jpdavis: xrandr --prop > > > > xrandr: Failed to get size of gamma for output default Screen 0: > > minimum 320 x 240, current 1280 x 720, maximum 1920 x 1200 default > > connected 1280x720+0+0 0mm x 0mm > > > > Thus the actual dpi being used by the display is 192*1280/2560 = 96, > > not the 192 sent to x2goagent and reported by xdpyinfo. > > Your x2goagent is running using the correct (forced) 192 dpi as specified via the > command line. But your x2go window is much smaller than your native > desktop. > > I am not really sure what to do here. Maybe we should try to calculate the > window size in mm, pass that to x2goagent and let it recalculate the dpi itself. I didn't see any options to x2goagent for passing window size. I actually get something much more reasonable when I DON'T specify a DPI (see attachments); then xdpyinfo reports dpi of 75x75 and size 1280x720, but xrandr still says maximum resolution is 1920x1200. > > > attempting to change the resolution from inside the session... > > > > xrandr --size 1920x1200 works but keeps same actual dpi of 96 (so > > desktop is larger than my screen) > > I don't get that. How can the desktop become larger than the screen? > The window size of your x2go session is the size of the xserver the MATE > desktop sees. The dpi setting should - from my understanding - influence the > selected fonts and maybe scaling, but not the overall size of the desktop. > > Can you please provide some screen shots to minimize miunderstandings? By "screen" I mean the physical laptop display panel. I have attached three fullscreen (2560x1440) images (taken on the laptop using Windows Snipping Tool) to this e-mail, I don't know if they will show up in the mail list (if not, well unfortunately I don't have anywhere I can put them publicly to link to), but at least you should receive them. Capture_x2go_default_setdpi192.PNG = case with client "set display dpi" turned on and equal to 192, in which the X session thinks the display is 1280x720 at 96 dpi. Capture_x2go_1920x1200setdpi192.PNG = what I see after issuing the command "xrandr --size 1920x1200" in the session; this is what I meant by desktop larger than the physical screen. Capture_x2go_default_nosetdpi.PNG = case with client "set display dpi" turned off, in which the X session still thinks the display is 1280x720 but at 75 dpi. This is better than the forced-dpi=192 cases, but still doesn't look like it's actually using the full resolution of the laptop. So with some more research I have learned that the apparent 96 dpi I'm seeing is actually forced by gdm via gnome-settings-daemon for all X sessions, as explained in the comments at https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/xsettings/g…. On the server, Xorg.0.log shows that Xorg correctly finds resolution (3840x2160) and dpi (139x137) of the attached monitor; but xdpyinfo shows dpi=96. Perhaps the remote X session generated by the x2go login is using the physical size of the laptop screen but with dpi=96 to arrive at 1280x720. I believe that when I force dpi=192, gdm automatically applies a scaling of 2, which would explain why everything is so huge in that case. One thing I don't understand very well is the relationship between X running on the x2go server machine and X (in this case VcXsrv) running on the x2go client machine. I have toyed with the idea of putting an xrandr command in a display-specific script under /etc/gdm/ to set up the screen for my remote sessions (I only ever have one running, and it's always display :10), but I haven't actually tried this yet. > Also, can you please retry using the current developer version of nx-libs as > described here: > http://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting I made an attempt at this using the instructions in the README file (https://github.com/ArcticaProject/nx-libs) to create rhel/centos/fedora rpms, but I got an error from the mock --buildsrpm command; I think I was supposed to actually build the libraries first (using make all), so I'll try that and report back. Jean-Paul

1 0

md5 and sha1 checks
by Jeff Sadowski 03 Apr '17

03 Apr '17

I was wondering if the person building the binaries could put those (md5 and sha1 sums) both on a page that is gpg signed? Then as I get to know the person building the binaries and if the key changes I can be suspicious of someone putting up another binary.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user