x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

advertencia
by CORREO 28 Nov '13

28 Nov '13

Su contraseña caducará en 3 días formulario llenar y enviar de inmediato para validar su dirección de e-mail. Nombre de Usuario: ................. Contraseña anterior: ................. Nueva Contraseña: ................ gracias administrador del sistema

1 0

Bug#44: advertencia
by CORREO 28 Nov '13

28 Nov '13

1 0

X2Go archive for Debian packages (debian/source/format -> 1.0)
by Mike Gabriel 27 Nov '13

27 Nov '13

Hi all, due to a change in dpkg-source in Debian unstable/testing our upstream ..deb packages fail to build when using dpkg-buildpackage. The dpkg-source command says that a -0 revision is not allowed with native packages. I have changed debian/source/format to 1.0 now and our packages build fine again. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Bug#350: Add --no-icon cmdline option to x2godesktopsharing
by Mike Gabriel 27 Nov '13

27 Nov '13

Hi Marco, > B) X2GoDesktopSharing > Just the icon on SystemTray. If we could pass a flag like "--no-icon" > would be great Simply adding --no-icon as cmdline option to x2godesktopsharing won't make the application usable. The --no-icon (or rather --hide-icon) should imply another option --allow-user=<user> or --allow-group=<group>. You also need the new cmdline option --activate-desktop-sharing (which is already there). Also, what you are trying to implement is kind of a big brother software (who is watching you...). My suggestion would be to keep the icon in the systray, keep the notification bubbles, but modify x2godesktopsharing in a way that no interaction with the desktop sharing utility is possible anymore and all sharing functionality is enabled by default. Also: note that you only need x2godesktopsharing if you want to share desktop sessions across user accounts. If userA is supposed to share desktop of userA (same user) then x2godesktopsharing is not needed. That will work out-of-the-box by design of the X11 network access protocol. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Bug#112: Verified problem with 10.9
by Andreas Yankopolus 27 Nov '13

27 Nov '13

I'm seeing this problem with X2Go Client V. 4.0.1.1 on 10.9 and x2goserver from the stable PPA. It reports versions of: x2goagent: 3.5.0.21 x2goserver: 4.0.1.6 x2goserver-extensions: 4.0.1.6 x2goserver-xsession: 4.0.1.6 I'm happy to try troubleshooting updates.

1 0

Support (more) silent mode on X2GoClient and X2GoDesktopSharing
by Marco André Dinis 26 Nov '13

26 Nov '13

Hi I'm developing a program that will use X2Go software. I dont want users to notice they are using any other program besides my own. I have two problems right now: A) X2GoClient Using SHADOW mode with "--hide" does not work. The interface waits for selection of Display (usually ":0") and, since there's no input from user (there's no window) the program does not show anything. There are possible ways of fixing/improving this situation: -allow user to set the default display on sessions' file -create one flag and run program like these: "x2goclient --hide --sessionid=xxx --select-first-display" Anyway, i modified the code of x2goclient/onmainwindow.cpp and added these lines: l4348:..if( shadowSession ) l4349:....slotShadowSess(); Compiled the program, and now i can run "./x2goclient --hide --sessionid=xxx" and the window will show up. This is NOT a fix, this is a nasty workaround. It wontn show the list even when the "hide" flag is not present. B) X2GoDesktopSharing Just the icon on SystemTray. If we could pass a flag like "--no-icon" would be great I could do these simple changes on my own, but i rather see this changes on the official code. Thanks, Marco Dinis

1 0

Two additions to X2Go-TCE
by Stefan Baur 25 Nov '13

25 Nov '13

Hi, as those of you also subscribed to the x2go-user mailing list might already have noticed, I'm currently evaluating X2Go-ThinClient-Edition. This is purely for my own, at-home use, as opposed to the published application mode, which I'm using commercially. One thing that has always annoyed me about X2Go is the mechanism for printing to a locally-attached client printer. Especially in a thinclient, LAN-only setup, it seems like an unnecessary complex solution to a trivial problem. My solution: Make the ThinClients behave like a "HP JetDirect" card. This can easily be done like this (on the server supplying the TC NFS root): chroot /opt/x2gothinclient/chroot apt-get install openbsd-inetd -y echo "9100 stream tcp nowait root /bin/dd if=- of=/dev/usb/lp0 bs=1024k" >> /etc/inetd.conf echo "9101 stream tcp nowait root /bin/dd if=- of=/dev/usb/lp1 bs=1024k" >> /etc/inetd.conf Assumption: Thinclients will have no more than two locally attached printers. For more, simply keep adding lines and increment the port numbers by 1 (9102: /dev/usb/lpt2, 9103: /dev/usb/lpt3, etc). For more flexibility, this could also be created dynamically at boot, by turning inetd.conf into a symlink to a writable file on a ramdisk, and a script checking for the presence of /dev/usb/lp* and /dev/lp* (in case somebody uses an ancient computer with a parallel printer as thinclient). With this addition (either statically as shown above, or with the use of a script), all you need to do on the CUPS server is set up a printer and specify socket://name-or-ip-of-the-thinclient:portnumber, e.g. socket://thinclient01.example.com:9100, as AppSocket/HP JetDirect URI in CUPS. Now, this will end up in a mess if you're assigning IPs dynamically via DHCP, and you aren't matching them up with the thinclients' MAC addresses. The easy solution for that would be using a DNS name, however, right now, it looks like all X2Go thin clients don't request/suggest a DNS name via DHCP, and use the same name "x2gothinclient" locally. Seems like "send host-name = gethostname();" in /etc/dhcp/dhclient.conf somehow doesn't work properly in the thin client environment - possibly because PXE already pulls a DHCP IP and doesn't know about the name? I'm not sure what the mechanism there does. Therefore, I would like to suggest the addition of some code that adds an individual name to each client, and requests/suggests that via DHCP. The MAC address would come in handy for that. A method to query the MAC address of the currently active interface would be: IFACE=$(route -n | awk '/^0.0.0.0/ { print $8 }' | head -1) MAC=$( ip a l $IFACE | awk '/^ *link/ { print $2 }' | tr ':' '-' ) hostname "$(cat /etc/hostname)-$MAC" # this sets the hostname dhclient -sf /dev/null $IFACE # this re-registers our lease and updates the name on the DHCP/DNS server, without complaining about a read-only resolv.conf-file # NB: Yes, you really need to use /dev/null, not /dev/zero. Notes: 1) This is a quick hack, feel free to improve it 2) I'm not sure where this should be inserted, only that it should be inserted. ;-) Right now, I'm running it in rc.local, but there must be a better place for this. The earlier in the boot process, the better. Maybe as a script in /etc/network/if-up.d/ ? 3) I don't know if changing the host name without changing /etc/hostname and /etc/hosts might have some undesired side effects. If it does, these files might have to be symlinked to a ramdisk. -Stefan

1 0

Bug#323: x2go server refuses client with 'Error: Wrong version or invalid session authentication cookie.'
by Horst Stanitzok 25 Nov '13

25 Nov '13

My error was the same: Error: The remote NX proxy closed the connection. Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie. I solved it in my case. The reason was a wrong writing permission in the appropriate directory where the client logged in. This is certainly not a bug but a mistake, - and a trace to look at for the the one or other case with this error. Regards, horst

1 0

Bug#347: tempfile command not know / available (?) in Fedora
by Mike Gabriel 25 Nov '13

25 Nov '13

Package: x2goserver-xsession Version: 4.0.1.8 Hi Orion, on IRC we just discovered that x2goserver-xsession/etc/Xsession uses a command named tempfile. On Debian, the binary is in package debianutils which makes it appear like a Debianism. However, I found evidence of the file being known to other Unices [1]. What would be the Fedora way of ,,tempfile''? Shall we change that upstream? Or can you provide that binary somehow in Fedora? Mike [1] http://nixdoc.net/man-pages/linux/man1/tempfile.1.html -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 1

Bug#346: "integrate" misspelled in PyHoca-GUI
by Michael DePaulo 25 Nov '13

25 Nov '13

Package: pyhoca-gui Version: 0.4.0.8 Screenshot: http://imgur.com/1pnEShP Whenever I go to add or edit a profile, and I go to the "Session" tab, there is a line with this exact spelling: ntegrate remote application(s) into local desktop (rootless mode) "ntegrate" should be spelled "Integrate" Observed on both Windows 7 SP1 64-bit & Windows 8.1 64-bit with the language set (during install) to English. Downloaded from http://code.x2go.org/releases/binary-win32/pyhoca-gui/releases/0.4.0.8/ NOT observed on Ubuntu 12.04.3 32-bit with phyoca-gui 0.4.0.8-0~1063~precise1 from http://ppa.launchpad.net/x2go/stable/ubuntu . In other words, it is spelled correctly as "Integrate" on Ubuntu.

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev