x2go-user March 2013

x2go-user@lists.x2go.org

23 participants
28 discussions

exotic multi-display / multi-monitor configuration
by Thomas Lutz 11 Mar '13

11 Mar '13

Hi everyone, is it possible to restrict a x2go session to a certain amount of moitors / displays? Usage: I got 4 monitors connected to to my developer machine. The goal is to use 3 monitors for one x2go session and 1 monitor for the local machine. Thanks for your help! Regards, Thomas

2 4

Host code.x2go.org temporarily offline today
by Mike Gabriel 10 Mar '13

10 Mar '13

Hi all, due to a potential hard disk failure the host code.x2go.org will be temporarily offline (at least) today. This affects: X2Go Bug Tracker X2Go package archives (Debian) X2Go Git ... Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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 2

Re: [X2Go-User] KMail composer window doesn't appear with NX
by John A. Sullivan III 08 Mar '13

08 Mar '13

On Fri, 2013-03-08 at 12:00 +0100, x2go-user-request(a)lists.berlios.de wrote: > Date: Thu, 7 Mar 2013 11:53:38 +0100 > From: Tristan Miller <psychonaut(a)nothingisreal.com> > To: x2go-user(a)lists.berlios.de > Subject: [X2Go-User] KMail composer window doesn't appear with NX > Message-ID: <201303071153.43213.psychonaut(a)nothingisreal.com> > Content-Type: text/plain; charset="us-ascii" > > Dear all, > > This message concerns a longtanding bug bothering KDE users. Most > likely > the bug is with KDE and not NX, but perhaps someone here can help us > find > out exactly what's causing the problem. > > First, a description of how things normally work with KDE's e-mail > client, > KMail: If one invokes the "New Message", "Forward", or "Reply" > command on > a message, a composer window opens. You can then type your message > and > send it, at which point the composer window closes. If you close > KMail > while one or more composer windows are still open, then the next time > you > launch KMail, those composer windows are restored so you can resume > writing > the messages where you left off. > > The problem is that if you launch KMail from an NX session, the > composer > window usually doesn't appear when you invoke the "Forward" or > "Reply" > commands. I think the composer windows must be created, but for some > reason they are not immediately visible, because if you quit and > relaunch > KMail (still over NX), the composer windows you created last time > suddenly > appear. > > The problem happens usually but not always. (That is, sometimes when > you > launch KMail, the Forward and Reply commands will work for a time, but > then > they'll stop working, and will never work again for that session.) > The > problem also never happens with the "New message" command, even though > to > all outward appearances the same sort of composer window is being > launched. > > So far I've reproduced the problem with both NoMachine NX and x2go. > > Anyone have any idea where the problem might lie? Is there some sort > of > fine-grained debug logging I can enable in x2go which prints a > message > every time it tries to display a new window? > > Regards, > Tristan Silly question on my part but is there any chance the composer window is appearing under another window, perhaps the mail KMail window? - John

2 1

Impossible to connect since update
by Saint Germain 07 Mar '13

07 Mar '13

Hello, I was happily using x2go between my Debian server and my Debian desktop since a few months when things stopped suddenly working after an update of both Debian yesterday (I haven't updated them since beginning of october). Debian server is with Debian stable (x2goserver) and Debian desktop is on Debian testing (x2goclient). Here are the version installed: x2goclient: 3.99.3.0-0~x2go1+squeeze~main~321~build1 x2goserver: 3.1.1.6-0~x2go1+squeeze~main~610~build1 Here are the logs I am getting on Debian server: sshd[11491]: error: connect_to localhost port 30001: failed. sshd[11491]: error: connect_to localhost port 30001: failed. sshd[11491]: error: channel 0: protocol error: close rcvd twice sshd[12040]: Accepted publickey for user from 92.226.X.X port 55500 ssh2 sshd[12040]: pam_unix(sshd:session): session opened for user user by (uid=0) sshd[12079]: error: bind: Address already in use sshd[12079]: error: channel_setup_fwd_listener: cannot listen to port: 30002 sshd[12079]: Received disconnect from 92.226.X.X: 11: Bye Bye sshd[12040]: pam_unix(sshd:session): session closed for user user sshd[11491]: channel_by_id: 0: bad id: channel free sshd[11491]: Disconnecting: Received ieof for nonexistent channel 0. sshd[11483]: pam_unix(sshd:session): session closed for user user And here are the logs I am getting on Debian desktop: Loop: PANIC! The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. I have checked that nothing is running on Debian server on port 30001 and I have restarted the SSH server, the x2go server and deleted .x2go directory on both Debian but errors are still the same. Can someone help me debug this ? Thanks

5 9

KMail composer window doesn't appear with NX
by Tristan Miller 07 Mar '13

07 Mar '13

Dear all, This message concerns a longtanding bug bothering KDE users. Most likely the bug is with KDE and not NX, but perhaps someone here can help us find out exactly what's causing the problem. First, a description of how things normally work with KDE's e-mail client, KMail: If one invokes the "New Message", "Forward", or "Reply" command on a message, a composer window opens. You can then type your message and send it, at which point the composer window closes. If you close KMail while one or more composer windows are still open, then the next time you launch KMail, those composer windows are restored so you can resume writing the messages where you left off. The problem is that if you launch KMail from an NX session, the composer window usually doesn't appear when you invoke the "Forward" or "Reply" commands. I think the composer windows must be created, but for some reason they are not immediately visible, because if you quit and relaunch KMail (still over NX), the composer windows you created last time suddenly appear. The problem happens usually but not always. (That is, sometimes when you launch KMail, the Forward and Reply commands will work for a time, but then they'll stop working, and will never work again for that session.) The problem also never happens with the "New message" command, even though to all outward appearances the same sort of composer window is being launched. So far I've reproduced the problem with both NoMachine NX and x2go. Anyone have any idea where the problem might lie? Is there some sort of fine-grained debug logging I can enable in x2go which prints a message every time it tries to display a new window? Regards, Tristan -- _ _V.-o Tristan Miller >< Space is limited / |`-' -=-=-=-=-=-=-=-=-=-=-=-=-=-=- <> In a haiku, so it's hard (7_\\ http://www.nothingisreal.com/ >< To finish what you

1 0

encrypting home & printing problem
by senrabdet＠aol.com 06 Mar '13

06 Mar '13

Hi All: We're experimenting with using X2go and encrypting /home with Encfs and so far everything works well except printing. We think this is because x2go printing relies on creating a link from the spool inside of the .x2go sub folder "C-User-50-xxxxxxxx.stDGNOME_dp32 to the /tmp area, and the Encfs encryption moves things and breaks the link. Our testing indicates that if we don't encrypt a user's /home we can print, but can't print if we encrypt another user's /home all on the same server. FYI: We're not using a central x2go printing server solution (we had concerns about security, so are taking the performance hit instead). We're using ssh to connect, and have gotten this to work by moving the ssh key outside of the encrypted area and creating a symlink to .ssh inside the area. Q: Would some sort of symlink work for printing? The issue here is that (and we may be wrong) the name of the "C-User50...." folder seems to change periodically. Would we need some sort of login script to figures out what the newest "C-user" folder is and creates a symlink on the fly to the spool device? As usual, any help appreciated!

1 0

Xauthority relocation
by Diego Lendoiro 06 Mar '13

06 Mar '13

Hello everyone; I'm trying to force x2go to use a Xauthority file different from the one located in $HOME I have googled a lot and I have found a patch has been included since 3.1.0 for doing this kind of setup. (I'm currently using x2goserver 4.0) I'm setting Xauthority file location through /etc/ssh/sshrc and every user exports $XAUTHORITY in their ~/.bashrc file. The problem is when I start the session with x2goclient it automatically exits without even entering xfce desktop. All the log I get is this from x2goclient : http://pastebin.com/CGTXZRC8 Any idea will be appreciated. Regards. -- Diego Lendoiro Inestable GNU/Linux Users Group Member | http://www.inestable.org In the beginning was the command line

1 0

Fwd: [X2Go-Dev] x2go wiki is moving...
by Mike Gabriel 04 Mar '13

04 Mar '13

Forwarding the below info to the x2go-user ML... Mike ----- Weitergeleitete Nachricht von heinz-m.graesing(a)obviously-nice.de ----- Datum: Mon, 04 Mar 2013 08:58:09 +0100 Von: "Heinz-M. Graesing" <heinz-m.graesing(a)obviously-nice.de> Antwort an: x2go-dev(a)lists.berlios.de Betreff: [X2Go-Dev] x2go wiki is moving... An: x2go-dev(a)lists.berlios.de Hello *@list, The wiki platform we are using will be moved to our dev server in the next days. This means, that for a time of a few days to weeks, the dns entries will be changed and regarding to the place where you accessing it, there will be different sites... To avoid loosing work, I'll deny changes to the old wiki. As soon as you can access the new location, you'll be able to work on the wiki again. In the last weeks I've done a rework of our wiki (technical and optical). As there were used now unsupported extensions and a not easy to update template, I changed to a near generic template and banned all unsupported extensions. The wiki technical base is a new installation, but I've imported all existing pages. Maybe there is some more work needed due to the lack of extensions and the new template. Besides those tasks, there is still a lot of work to do to, to get a better "first impression" on the x2go project. As there were a lot of fake users, we'll disable the "registration" feature of the wiki. People who would like to help are invidted to write a short email on our dev/user lists, so we can avoid "capture pictures" and other annoying things. If you can't loging anymore it is likely that you never changed or added content to the wiki. I've removed those and accounts that created "advertising" pages. As the work is not completed yet, I hope it will still seen as progress. Regards, Heinz _______________________________________________ X2Go-Dev mailing list X2Go-Dev(a)lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev ----- Ende der weitergeleiteten Nachricht ----- -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user March 2013