x2go-user

x2go-user@lists.x2go.org

2315 discussions

PyHoca-GUI 0.4.0.1 created bad config file
by Dirk Eddelbuettel 14 Mar '13

14 Mar '13

Hi all, x2go is quite nice to connect from Windoze to a few Ubuntu machines at work, and I am very glad that you guys carry on from the various Nx projects In order to permit multiple machine entries, I fiddled with PyHoca (0.4.0.1), but seem to have corrupted the file by adding multiple entries with the same key. Now I am getting: Traceback (most recent call last): File "pyhoca\wxgui\frontend.pyo", line 1064, in OnProfileEdit File "pyhoca\wxgui\profilemanager.pyo", line 137, in __init__ File "x2go\backends\profiles\_file.pyo", line 329, in to_profile_id x2go.x2go_exceptions.X2GoProfileException: The sessions config file contains multiple session profiles with name: foo123 Traceback (most recent call last): File "pyhoca\wxgui\frontend.pyo", line 1147, in OnProfileExport Where (on a win7 machine) is that file, and how can I clean it manually? Many thanks, Dirk

2 3

Unity and LXDE with x2go - a quick test
by Christoph Mathys 14 Mar '13

14 Mar '13

I ran some tests from Windows and Ubuntu trying to start Unity and LXDE sessions on Ubuntu 12.04. The findings: - LXDE and x2go work OK. - Unity is IMO close to unusable with x2go. Setup: Ubuntu 12.04 with x2goclient 4.0.0.4, x2goserver 4.0.0.0-0~640~precise1 Windows 7 with x2goclient 4.0.0.3. Unity Open (Linux/Windows): The window is resized to fullscreen during session startup, completely ignoring whatever resolution I might have chosen in the settings. Resize(Linux/Windows): Resizing the Unity window does not work, e.g. the window size changes but the content "does not get it". LXDE Open (Linux): Works correctly. Open (Windows): The client window is too small for the content. Presumably [0]. Resize (Linux/Windows): When resizing the client window, the taskbar is "forgotten". It just stays where it is while the rest is resized. I can trigger the taskbars resize reliably when I open a new window or move the mouse over buttons on the taskbar that change their appearance on mouseover. [0] http://lists.berlios.de/pipermail/x2go-dev/2012-January/003213.html Christoph

2 6

X2Go Client Usage page on the wiki
by Mike Gabriel 14 Mar '13

14 Mar '13

Hi all, There is one page that is really important but totally bullshit on our wiki: http://wiki.x2go.org/doku.php/usage:x2goclient Can someone fix this page (any X2Go user can do that). Make some nice screen shot, explain how to configure your first session, etc. THANKS SO MUCH!!! Mike (with his delegating hat on) -- 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 4

Disable x2goclient audio support? (bluetooth headset trouble)
by Christoph Mathys 14 Mar '13

14 Mar '13

I use a bluetooth headset for music and voip. When I start x2goclient on Windows 7, it forces the headset into a low-quality profile (no session is open, just the client). This is expected to happen if an application wants to use the microphone. I presume x2go opens audio sources and sinks in order to forward them to a client later and so Windows thinks it needs to switch to another profile. When I close x2goclient again, the headset switches back to the high quality profile. I can disable the headsets microphone manually inside the windows audio settings. But then, of course, I can no longer use the microphone for voip. It would be nice to have some kind of switch to disable x2gos audio support completely (or to be able to select which devices are forwarded). As a workaround, it seems to work if I just rename pulseaudio.exe to something else. Thanks! Christoph

2 1

Workaround/fix for GNOME3 Issue (Bug #42)
by tech mailinglists 12 Mar '13

12 Mar '13

Hello all, I have a short question: Is there a workaround or fix for the GNOME3 Issue (described in Bug #42)? Best Regards

1 0

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user