Hi Daniel,
On Di 04 Okt 2011 19:21:13 CEST Daniel Lindgren wrote:
> Still having problems, I can log in but sessions die on me several
> times a day.
>
> Server side auth.log, at the time of session crash:
>
> Oct 4 18:46:45 fileserv gnome-keyring-daemon[5990]: dbus failure
> unregistering from session: Connection is closed
> Oct 4 18:46:45 fileserv gnome-keyring-daemon[5990]: dbus failure
> unregistering from session: Connection is closed
> Oct 4 18:46:46 fileserv sshd[23183]: Received disconnect from
> 192.168.0.103: 11: disconnected by user
>
> daemon.log:
>
> Oct 4 18:46:45 fileserv gnome-session[5975]: WARNING: Detected that
> screensaver has left the bus
>
> The ~/.x2go/<session>/session log on my client:
>
> NXPROXY - Version 3.5.0
>
> Copyright (C) 2001, 2011 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Proxy running in client mode with pid '17564'.
> Session: Starting session at 'Tue Oct 4 18:33:23 2011'.
> Info: Connecting to remote host 'localhost:30201'.
> Info: Connection to remote proxy 'localhost:30201' established.
> Loop: WARNING! Disabling NX delta compression.
> Loop: WARNING! Disabling use of NX persistent cache.
> Info: Connection with remote proxy completed.
> Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming
> agent session.
> Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming
> agent session.
> Info: Using LAN link parameters 1536/24/1/0.
> Info: Using pack method '16m-png-9' with session 'unix-kde-depth_32'.
> Info: Not using NX delta compression.
> Info: Not using ZLIB data compression.
> Info: Not using ZLIB stream compression.
> Info: Not using a persistent cache.
> Info: Forwarding X11 connections to display ':0.0'.
> Session: Session started at 'Tue Oct 4 18:33:23 2011'.
> Info: Established X server connection.
> Info: Using shared memory parameters 1/2048K.
> Proxy: PANIC! Failure reading from the peer proxy on FD#5.
> Error: Failure reading from the peer proxy.
> Loop: PANIC! No shutdown of proxy link performed by remote proxy.
> Error: Connection with remote peer broken.
> Error: Please check the state of your network and retry.
> Session: Terminating session at 'Tue Oct 4 18:46:48 2011'.
> Session: Session terminated at 'Tue Oct 4 18:46:48 2011'.
> NXTransDialog: WARNING! Couldn't start '/usr/NX/bin/nxclient'. Error
> is 2 'No such file or directory'.
> Warning: Couldn't start '/usr/NX/bin/nxclient'. Error is 2 'No such
> file or directory'.
> NXTransDialog: WARNING! Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games'.
> Warning: Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games'.
> NXTransDialog: WARNING! Couldn't start 'nxclient'. Error is 2 'No such
> file or directory'.
> Warning: Couldn't start 'nxclient'. Error is 2 'No such file or directory'.
> NXTransDialog: WARNING! Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games'.
> Warning: Trying with path
> '/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/NX/bin:/opt/NX/bin:/usr/local/NX/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games'.
>
> The session is completely gone from the server, as if I'd logged out.
>
> I have the latest nightly packages installed (ie x2goagent 3.5.0.5) on
> both client and server.
>
> Cheers,
> Daniel
we ourselves are neither really happy about the changes in nxagent and
we will have to take a closer look still. Note, the nightly builds are
the developers' testing packages.
Currently, x2goagent from nightly builds is not at all recommended.
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…
hi devs,
last week Alex and I talked about shorter nano release cycles and thus
shorter cycles of declaring code as stable.
Currently, there is no automation and mostly I urge ourselves to
declare code as stable. Some projects are actually releasable but do
not get released as they get forgotten (e.g. the PXE project
x2gothinclient.git).
What Alex and I came up with and what I would like to shorly discuss
here is a more automated, but still humanly triggered mechanism.
The version number of Git projects in X2go Git that
(a) are usable
(b) are not obviously broken/buggy/instable
(c) have not been worked on for 2 weeks
(d) have been tested (at least by me and somebody else)
will get incremented in the last digit (1.2.3.x -> 1.2.3.y) after
these two weeks, packages will be declared as stable and provided in
the corresponding repositories.
The shorter release intervals will allow us to keep a better track of
the milestones within the projects we have made. I partly consider
this as a facility of documentation (that is: documenting usable
states of the code).
Discussion+feedback welcome,
Mike
PS:
The first release day can already be tomorrow:
x2gothinclient
x2goclient
cups-x2go
A week from tomorrow:
x2goserver
x2gognomebindings
x2golxdebindings
x2goagent (bug fix release currently being prepared by Alex)
nxcomp
nxcompext
nxcompshad
nxproxy
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…
Hi All,
We have developed a simple pyhoca mac version for lion and snowleopard. This is geared towards our way of working (rootless), but should be usable for others if they know something of Mac packaging.
Met vriendelijke groet,
Dick Kniep
Lindix BV
tel. 036-5215580
mob. 06-50991858
-----Oorspronkelijk bericht-----
Van: Mike <mcescalante(a)gmail.com>
Verzonden: vr 16-09-11 02:05:23
Aan: x2go-dev(a)lists.berlios.de;
Onderwerp: [X2go-Dev] x2go for OSX Lion?
Is there a planned release for a x2go client for Mac OSX Lion?
Thanks!
_______________________________________________
X2go-Dev mailing list
X2go-Dev(a)lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
!DSPAM:4e7292c3154531336712104!
Hi everyone,
I've been trying to create a "portable" x2go configuration file in order
to send it by mail to a remote user (as one would do with a nxclient
.nxs configuration file), but I have not been able to get do it (and
asking our dear friend google didn't helped either).
Could anyone point me in the right direction?
cheers, and keep on the good work!
Denis
--
Denis Cardon
Tranquil IT Systems
44 bvd des pas enchantés
44230 Saint Sébastien sur Loire
tel : +33 (0) 2.40.97.57.57
http://www.tranquil-it-systems.fr
Hi all,
yesterday I have been working on the C++ code in x2godesktopsharing.
To make sure that x2godesktopsharing really gets shutdown on
x2goterminate-session, I have added a script to the x2godesktopsharing
package that detects the corresponding x2godesktopsharing process for
a given session $X2GO_SESSION. This script
,,x2godesktopsharing-terminate" will be exectuted by
,,x2goterminate-session".
This brought up the next question: how do we want to handle
x2godesktopsharing while a session is suspended. This older versions
of X2go (I think) this has been possible. I consider this as a
security problem and something that most users do not want. Imagine
the scenario:
o start x2go session
o start x2godesktopsharing
o allow user foo to share your desktop and remember this setting permanently
(via .x2godesktopsharing/settings)
o suspend your session (and x2godesktopsharing continues to offer desktop
sharing... :-( )
o user foo tries to connect to your desktop while you are away (while
your session is suspended
o -> this is YUK!
So what I have done is this:
o on session suspend, terminate x2godesktopsharing and remember that it was
running, place a server-side empty file ,,resume-desktopsharing'' into
$HOME/.x2go/C-$X2GO_SESSION/
o on session resume, check if that file is there and if so, launch a new
instance of x2godesktopsharing, with sharing mode set to disabled.
Feedback, comments?
Mike
PS: I have just looked at my commits from yesterday and it feels like
I should rename the provided scripts in this way:
x2godesktopsharing-terminate -> x2goterminate-desktopsharing
x2godesktopsharing-suspend -> x2gosuspend-desktopsharing
etc.
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…
Hi all,
we would like to set up an i18n team for X2go.
The task of this team will be the maintenance of translation files in
all X2go projects that utilize translation mechanism. Do I need to be
able to read and write code for this? Definitely, no! Become a member
of a translation team is a possibility to be in close contact to the
developer team without necessarily being able to code. Only
pre-requisite: you use X2go quite regularly and no the functionalities
of the X2go components... plus: your English is good enough to find
good translations of menu items, dialog boxes, etc.
Each translator is responsible for the translation files of his/her
language. Of course, it is also possible to maintain one translation
language as a sub-team (that is: one language is maintained by more
than one person).
Currently these applications are using translation features:
x2goclient
pyhoca-gui
x2gognomebindings
plasma-widget-x2go (KDE$ binding)
x2godesktopsharing
x2goadmincenter
... (possibly more to come) ...
The idea is to have a dedicated mailing list for announcing x2go-i18n
issues (mostly mails like: ,,i18n Team, please translate
this-and-that'' and a permanent team (with fluctuations, if needed,
but preferably not so much fluctuation among the team members) that
feels responsible and dedicated to providing a multi-lingual X2go
environment to the world.
The tools that we use for translations are currently versatile.
Depending on the team we will find ways to standardize the translation
technologies (if the team members are flexible with using different
i18n tools, then this may not be needed).
So, if you are interested in contributing translations to X2go and
join the development realm by this approach, please-please-please
subscribe to
http://lists.berlios.de/mailman/admin/listinfo/x2go-i18n
and ping us developers on that list.
Thanks in advance for your time!!!
Mike (and Heinz)
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…
Hi all,
my suggestion for starting with the X2go i18n subproject is as follows:
o developers will provide a README.i18n file in each relevant
project folder of X2go Git, this README will explain the translation
mechanisms and files of that very project
o translators give feedback on the readability of the docs ;-)
o translators start the work and follow the steps in the README.i18n files
Till now, there have been not been so many subscription on x2go-i18n,
so if you feel called, please subscribe!!!
http://lists.berlios.de/mailman/listinfo/x2go-i18n
As an example of such a README.i18n, I have provided one for the
pyhoca-gui.git project:
http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=blob;f=README.i18n;h=56dfce2…
Thanks a lot for your contributions!!!
Mike
PS: We will investigate a translation service, but in my opinion the
bugtracker question (which is still open) is far more urgent.
PPS: (As a side-note: Currently, Heinz is heavily working on your web
presentations: the wiki, the blog, merging homepage into the wiki,
hosting, etc. So this part currently has top priority here.)
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…
Hi Alex,
today I have implemented basic X2go desktop sharing client support in
Python X2go. The commit I already uploaded to X2go Git is very basic
and needs quite some fine-tuning and testing before I will weave it
into PyHoca-GUI. However, with pyhoca-cli it is already possible to
test the desktop sharing client code in Python X2go.
While working on that I have encountered two problems, though:
1.
When the x2godesktopsharing tray applet gets killed by SIGTERM it does
neither remove its socket file /tmp/x2godesktopsharing_... nor its
lock file...
As a consequence, the x2golistdesktops script returns stale desktop
sessions resulting from stale x2godesktopsharing lock/socket files.
x2godesktopsharing only removes its socket/lock files if the
,,Beenden'' item in the applet's tray menu is clicked.
2.
When connecting to x2godesktopsharing the x2godesktopsharing applet
always shows wrong username:
(a) session already running as user-a, start x2godesktopsharing
(b) connect a shadow session to user-a's session (as user-b)
(c) user-a then gets asked if it will accept an incoming connection
from user-a(!!!!), here it should ask for user-b instead
The basic question here is a question of concept. I currently only see
this approach:
(i) -> pass another parameter from x2gostartagent to
x2godesktopsharing (client
mode), this parameter will be a representation of the connecting user
name (and maybe gecos field?)
It would be good to fix both issues some time in the near future.
Apart from these two issues x2godesktopsharing works brilliantly.
Another cosmetic change could be an improvement of
x2godesktopsharing's whitelist/blacklist editor (e.g. add users
manually, maybe even add groups manually etc.). But that is rather of
a lower priority...
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…