* On 6/10/23 17:37, Buddy Butterfly wrote:
> also tested it on a Ubuntu Trusty (18.04) system.
> It does not work there yet!
Thanks for testing. Oh, that's right. For Ubuntu, I've only built release/stable
KDrive packages for Jammy (20.04), Kinetic, Lunar and Mantic.
Unfortunately, X2Go Server al
* On 6/6/23 15:52, Buddy Butterfly wrote:
> just revert to the previous version for the time being with pinning it:
>
> Create file pin-x2go in /etc/apt/preferences.d/ with content:
Please try unpinning.
Now that we have X2Go KDrive builds, and I have fixed up the brokenness in the
Debian build
* On 5/31/23 10:39, Enrico Baravoglia | Fucine.IT wrote:
> Hello everyone.
>
> We have this remote desktop (with x2go-server running there):
>
> * Operating System: Kubuntu 20.04
> * KDE Plasma Version: 5.18.8
> * KDE Frameworks Version: 5.68.0
> * Qt Version: 5.12.8
> * Kernel Version:
* On 5/19/22 9:22 AM, richard lucassen wrote:
> @ the Debian repository admin:
>
> When running "apt update" I get this warning:
>
> W: Conflicting distribution: http://packages.x2go.org/debian stable
> InRelease (expected stable but got buster)
>
> In /etc/apt/sources.list.d/x2go.list I have:
* On 5/10/21 11:38 PM, Mike Gabriel wrote:
>> Just looking to upgrade to nightly on a CentOS7 system. I have the
>> repo file installed. I disabled the default and enabled the nightly
>> and gave it the old "yum update "x2go*"
>>
>>
>> There is no package in standard repos that I could find n
* On 8/16/20 8:42 AM, Tamir Einy wrote:
> I have installed latest nightly build (4.1.2.3) that you provided, the
> connection to the server failed,
>
> Here is the debug output to the command:
>
> x2go-INFO-1> "Starting X2Go Client 4.1.2.3..."
> x2go-WARNING-1> English language requested, not l
* On 4/23/20 6:16 PM, Oleksandr Shneyder wrote:
> yes, the community installer of Windows X2Go Client doesn't contain
> x2gokdriveclient binary yet. I can't tell you why, apparently Mike
> didn't have time to build it or maybe he just forgot about it. Looks
> like x2gokdrive isn't really important
* On 2/10/20 2:47 AM, Ingo Brückl wrote:
> Are there plans for a new release of the Windows client
> (with current VcXsrv)?
Yes, very soon™.
I'm working on it. Desperately need it for other operating systems as well.
Hopefully done tomorrow or at least very soonish.
Mihai
signature.asc
Desc
ttp://www.nomachine.com
> <http://www.nomachine.com/>)
> Copyright (c) 2008-2014 Oleksandr Shneyder <mailto:o.shney...@phoca-gmbh.de>>
> Copyright (c) 2014-2016 Ulrich Sibiller mailto:ul...@gmx.de>>
> Copyright (c) 2014-2016 Mihai Moldovan <mailto:io...@ion
* On 6/1/19 2:44 AM, Spenser Gilliland wrote:
> I'm having an issue installing the x2gobroker-agent package on CentOS 7. It
> looks like CentOS 7 has a python36 package but not a python3 (and various
> python
> packages).
Yeah, x2gobroker is broken on CentOS/EPEL since the Python 3 port. Unfortu
* On 6/6/19 7:52 PM, Robert Kudyba wrote:
> We're still seeing:
>
> Failed to synchronize cache for repo 'x2go-nightly-fedora'
> Failed to synchronize cache for repo 'x2go-extras-fedora'
> Ignoring repositories: x2go-nightly-fedora, x2go-extras-fedora
>
> Does that mean we have to import the new
* On 5/31/19 4:15 AM, Robert Kudyba wrote:
> Been seeing these errors from def update for the past few nights:
>
> Failed to synchronize cache for repo 'x2go-nightly-fedora'
> Failed to synchronize cache for repo 'x2go-extras-fedora'
> Ignoring repositories: x2go-nightly-fedora, x2go-extras-fedora
* On 5/31/19 6:10 AM, Chris Puttick wrote:
> Or possibly not expired, broken. FF refuses to continue with
> SEC_ERROR_UNKNOWN_CRITICAL_EXTENSION, but Chromium shows the
> certificate as in date, but reports NET::ERR_CERT_INVALID.
Both. I knew that it would expire and it didn't automatically renew
* On 3/28/19 10:40 PM, Ingo Brückl wrote:
> I tried "custom desktop" and simply gave "sh /home/me/.xinitrc" as an
> experiment. Everything shows up like my local desktop with two exceptions.
> Xterm is a very small window with small font in it (as if my X resource
> XTerm.VT100.font: 10x18 would be
* On 3/28/19 6:44 PM, Ingo Brückl wrote:
> Is x2goruncommand line 245 ("$dmd" == "IceWM") a typo (dmd instead of cmd)?
Yes, but it's not critical since X2Go Client has a bug (at least I would
categorize it as such) that maps names back into full commands.
I fixed that up in
https://code.x2go.org/
* On 3/22/19 11:53 AM, Ulrich Sibiller wrote:
> Well, all I know is this (from
> https://wiki.x2go.org/doku.php/wiki:repositories:suse):
> "Currently, the OBS SUSE X2Go instance is stale. The packages are only
> being updated irregularly and support will likely not be provided.
> This note will be
Hi
In order to lower resource stress when building packages, I plan to deprecate
support for distributions that have reached End Of Life on December 31th 2018.
This includes the following distro versions:
- Fedora
o 26
o 27
- OpenSuSE
o 42.1
o 42.2
- SLES
o 12.0
Ubuntu builds are cea
* On 09/11/2018 08:02 PM, EI wrote:
> I have a very strange problem with x2goserver running on Ubuntu 18.04. I get
> an
> error message on the client side when I try to suspend the connection. I also,
> can't reconnect to existing connections. I haven't had this problem with
> 16.04.
>
> I tried
Hi
Our current active Swedish translator stepped down recently.
On behalf of the project, I am looking for someone to replace him and continue
the well-maintained Swedish translations.
If you are interested to help, please subscribe to the i18n mailing list[0].
More information regarding the t
* On 04/27/2018 12:30 PM, Mario Brese wrote:
> is there any way to see the client version who is connected, on the server?
There's not. This information is not exposed anywhere, and, for what it's worth,
never queried by X2Go Server since it's not needed.
OT: please don't thread-hijack the next
* On 04/15/2018 04:59 AM, Qianqian Fang wrote:
> thank you so much! the /usr/lib/x86_64-linux-gnu in the LD_LIBRARY_PATH
> was indeed the culprit! after removing it, I am now able to log in all my
> servers!
>
> I checked my file modification history for .bashrc, I added this path for a
> subset o
* On 04/15/2018 01:39 AM, Qianqian Fang wrote:
> ||<
> LD_LIBRARY_PATH=/usr/local/cuda/lib64:/usr/lib:/pub/lib:/pub/cuda-7.5/lib64:/space/hoyi/1/users/shared/mesa-10.1.3:/usr/lib/x86_64-linux-gnu/mesa:/usr/lib/nvidia-375:/usr/lib/nvidia-387:/usr/lib/nvidia-384||
> ||---||
> ||>
> LD_LIBRARY_PATH=/u
* On 04/13/2018 01:54 PM, Bas van den Heuvel wrote:
> In the past, I edited /usr/bin/x2gostartagent and removed the "-nolisten
> tcp" part, and edited /etc/x2go/x2goagent.options to remove "-nolisten tcp"
>
> It's not working, even a simple xeyes docker fails to open display:
>
> vdheuvel@arthur
* On 04/13/2018 11:30 PM, Roger Moye wrote:
> When we login to the server, the X2Go window appears as if the Linux desktop
> is
> about to appear and then the session is terminated.
>
> The only thing I see that is noteworthy in /var/log/messages on the server is:
>
> /usr/bin/x2goruncommand: db
* On 03/28/2018 02:58 PM, Ivan Gomez wrote:
> libNX_X11-3.5.0.32-3.el7.x86_64
> libNX_Xcomposite-3.5.0.32-3.el7.x86_64
> libNX_Xdamage-3.5.0.32-3.el7.x86_64
> libNX_Xdmcp-3.5.0.32-3.el7.x86_64
> libNX_Xext-3.5.0.32-3.el7.x86_64
> libNX_Xfixes-3.5.0.32-3.el7.x86_64
> libNX_Xinerama-3.5.0.32-3.el7.x8
* On 03/27/2018 03:09 PM, Ivan Gomez wrote:
> *Environment:*
>
> *Server:*
>
> Red Hat Enterprise Linux Server release 7.3 (Maipo)
>
> x2goagent: 3.5.0.32
>
> x2goserver: 4.0.1.20
>
> x2goserver-extensions: 4.0.1.20
>
> *Client:*
>
> * *Windows 7 & Windows 10
>
>
* On 03/26/2018 11:11 PM, Qianqian Fang wrote:
> I confirm that the server giving the first error, i.e. "The remote proxy
> closed
> the connection while negotiating..."
> has indeed installed an older version of libnx-x11 (3.5.0.33~710).
Hmm, mixing X2Go Server 4.1.0.0 and nx-libs 3.5.0.x is not
* On 03/26/2018 03:45 PM, Qianqian Fang wrote:
> I run a small cluster for my lab, including about 12 Linux boxes running
> Ubuntu
> 14.04 (1x with 16.04). We have been using x2go and ssh as the primary tool to
> access these computing resources.
>
> Recently (started a month ago), I noticed ther
* On 03/23/2018 10:10 PM, Michael Stauffer wrote:
> CentOS 7.4
>
> However when I try to connect with x2go client (4.1.1.1 on windows 10), I get
> a
> timeout. Connecting to our old x2go server works.
>
> I've disabled the firewall for testing but it still times out.
Such issues come up every no
* On 03/15/2018 05:23 AM, Norman Gaywood wrote:
> If I connect, suspend the session, resume the session. I can then move my
> session across screens.
> Worked for me a few times so far.
Hmm, I just tried that right now and couldn't. nxagent crashes, even after
suspending and resuming the session be
* On 03/15/2018 03:11 AM, Norman Gaywood wrote:
> So I've updated dev to the latest
> again 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27
>
> And I seem to get an nxagent segfault every time I move the session window
> into
> another screen.
>
> Same version in production and it was stable fo
* On 03/13/2018 02:41 PM, h i wrote:
> When using the ppa:x2go/stable repository, something seemed strange when I ran
> the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message
> about
> a partial upgrade I've never seen since using Ubuntu. I've attached the
> message.
> After ru
* On 03/09/2018 10:23 PM, h i wrote:
> I think I might have to roll-back to the previous x2goserver version. At
> least with our setup, we never had a flicker issue until this most recent
> update.
I know, it's a new issue that only manifests with the new nx-libs 3.5.99.x
release.
We currentl
* On 03/15/2018 01:16 AM, Nigra Truo wrote:
> [SOLVED]
>
> I figured out what the culprit is. This is an older system and the intent to
> purge was based on the assumption that some old config or other depricated
> element might be still hanging around. So doing this here:
>
> apt purge x2goserve
* On 03/14/2018 02:48 PM, Mihai Moldovan wrote:
> Please create /etc/x2go/x2gosql/sql manually with a line containing
> 'backend=sqlite'. That should allow you to purge the packages.
>
> Afterwards you should be able to reinstall them normally.
Oh, and if this still do
* On 03/14/2018 03:19 AM, Nigra Truo wrote:
> Thanks for the pointers. Yes, of course all apt commands are always executed
> as root. Right now it is not so much about the bug that prevents purging, it
> is more that I just can't reinstall x2goserver anymore. I see this message
>
> "X2Go is config
* On 03/11/2018 09:44 AM, Robert Dinse wrote:
> Might be because of backports being enabled giving me a newer version of
> something:
>
> deb http://packages.linuxmint.com sylvia main upstream import backport
> enabled giving me a newer version of something? Or maybe my apt database
* On 03/13/2018 10:25 AM, Norman Gaywood wrote:
> But all those links/folders on http://snapshots.packages.x2go.org/ seem to be
> empty.
>
> Or am I missing something?
Nope, they are not. See for instance
https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/
It's just
* On 03/13/2018 07:34 AM, Norman Gaywood wrote:
> Last night after upgrading several Fedora 27 systems with the latest
>
> http://packages.x2go.org/fedora/$releasever/main/$basearch
>
> nxagent now segfaults sometimes on connection, sometimes when doing a move
> of the x2goclient screen.
>
> Pro
Hi
Since most browsers either stopped supporting NPAPI (or will be dropping support
with the next ESR version) and Qt 5 does not feature a browser plugin
architecture any longer, I will be ripping out code related to the X2Go Plugin
in the development version of X2Go Client soonish.
Expect the n
* On 03/11/2018 06:15 AM, Robert Dinse wrote:
> With xenial:
>
> apt install x2goserver x2gomatebindings x2golxdebindings --install-suggests
> --install-recommends --fix-broken --fix-missing
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Som
* On 03/11/2018 05:56 AM, Robert Dinse wrote:
> It got it to work, xenial was broken, and everything prior had wrong
> library version for the Mint 18.3 X-server. Since I am doing some work on
> the
> machine tonight I really needed it to work, it was either that or vnc which
> is
> ext
* On 03/11/2018 04:39 AM, Robert Dinse wrote:
> Also, all repositories older than artful wanted to use the 3.5.0 libs
> but need 3.5.99 to get the proper version of xrandr for Mint 18.3.
Switching to packages for a newer system version than you have isn't a good
idea...
I'll install a Mint
* On 03/08/2018 07:52 PM, Stefan Baur wrote:
> Could we change the mouse cursor over the sensitive area, maybe? Or,
> undo the change and go back to a fully sensitive tile, but change the
> mouse cursor once it hovers over an editable field?
The problem isn't visual indication and changing the mo
* On 03/07/2018 07:34 PM, h i wrote:
> I've been experiencing problems with opening applications and resizing my x2go
> client window after installing the newest version x2go-server.
>
>
> The issues occurs on Ubuntu 14.04 and 16.04.
>
>
> What happens now is that every time I maximize my x2go-
* On 03/04/2018 10:51 AM, Robert Dinse wrote:
> It hasn't happened to me so I don't know what the people are doing
> before
> it gets stuck, could be mate, kde, lxde, lfce, openbox, they're all on there.
> Next time it happens I'll trace it to see what it is doing.
Please follow https://git
* On 03/04/2018 01:54 AM, Robert Dinse wrote:
> Yes consuming a large amount of CPU and not doing anything useful,
> customer is disconnected. Connection is still possible but doesn't get rid
> of the stuck processes, I have to kill -9 to get rid of them.
Uhm... "stuck" is pretty ambiguous
* On 03/04/2018 01:35 AM, Robert Dinse wrote:
> We are seeing nxagent processes stuck running in a loop when the
> customer
> is no longer logged in.
Stuck in a loop, i.e., using a high amount of CPU resources and not doing
anything useful? Is connecting still possible? Does the usage retur
* On 03/03/2018 04:45 AM, Robert Dinse wrote:
>
> I have now had three different machines, a ubuntu server, a mint server,
> and a zorin server with the most recent builds installed display very strange
> behavior.
>
> Initially they work, I connect, and at some point during the sessi
* On 03/03/2018 01:49 AM, Robert Dinse wrote:
> Trying to install x2go stable x2goserver on Ubuntu 17.10 I am getting:
>
> The following packages have unmet dependencies:
> x2goserver : Depends: x2goserver-x2goagent (>=
> 4.1.0.0-0~1517~ubuntu17.10.1)
> but it is not going to be installe
* On 03/03/2018 12:37 AM, Robert Dinse wrote:
> Question: It appears that the various libs in lib-nx that used to be
> separate deb packages on Ubuntu/Debian, etc, have been replaces with a single
> nx-11-common package, is this correct?
Nope, wrong.
-common packages, as always in Ubuntu/De
* On 03/02/2018 12:18 PM, Stefan Baur wrote:
>> -After the most resent update:
>>
>> x2goagent : Depends: nxagent (< 2:3.5.0.33-0~710~ubuntu16.04.1.1)
>>
>> -however,
>> nxagent is already the newest version (2:3.5.99.14-0~816~ubuntu16.04.1).
>
> Please wait until all the builds have completed, the
* On 03/02/2018 07:37 AM, Robert Dinse wrote:
>
> The output of:
>
> dpkg -l | grep -iE '(x2go|nx)'?
>
> ... Was too large to post to the list so I've thrown it up on my ftp
> server, you can retrieve it from ftp.eskimo.com, username: anonymous,
> password: (your e-mail address
* On 03/02/2018 07:04 AM, Robert Dinse wrote:
>
> I just did:
>
> apt purge *x2go* nx* libnx*
>
> Followed by:
>
> apt install x2goserver --install-suggests --install-recommends
>
> And still get that same pop-up. This is on:
Hm, dpkg -l | grep -iE '(x2go|nx)'?
* On 03/02/2018 12:53 AM, Robert Dinse wrote:
> The nightly builds won't install and the stable doesn't work. When I
> try to login I get a pop-up:
>
> The remote proxy closed the connection while negotiating
> the session. This may be due to the wrong authentication
> credentials passed to
The deprecation has been fully finished.
Mihai
signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
* On 01/24/2018 08:36 AM, Robert Dinse wrote:
> Yes, you gotta love systemd. There is an upside though, it's about
> two seconds between the time my BIOS fires off the boot block and I've got a
> desktop login screen, under the old start up system it was more like 30
> seconds.
... unless
* On 01/22/2018 10:28 PM, Andrew Munn wrote:
> Thanks!
> I've added the following line to /usr/lib/tmpfiles.d/tmp.conf
>
> x /tmp/.x2go-*
>
> Hopefully that fixes it.
Then again, according to
https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
a
* On 01/16/2018 02:32 AM, Andrew Munn wrote:
> I get reasonable output from x2golistsessions_root. I also see a matching
> directory in /tmp/.x2go-$user/ containing 3 files:
>
> [root@hercules C-andrew-51-1513021653_stDMATE_dp24]# ls
> total 12
> -rw-rw-r-- 1 andrew andrew 1 Jan 10 08:56 option
* On 01/14/2018 04:22 AM, Robert Dinse wrote:
> Unfortunately, it created a different error:
All this code is new, so I'm not surprised. :)
> Connection failed. /usr/lib/x2go/x2gogetfreeport: line 47: typeset: '65535':
syntax error: operand expected (error token is "'65535'")
Hmm, that lin
* On 01/14/2018 03:51 AM, Robert Dinse wrote:
>
> Actually I totally purged everything and re-installed, no help.
Thanks for testing this stuff!
As root:
sed -i -e 's/get_random_port/get_pure_random_port/'
/usr/lib/x2go/x2gogetrandomport
I've also just pushed a commit fixing this issue,
* On 01/14/2018 03:28 AM, Robert Dinse wrote:
> After installing updates today Ubuntu 17.10 server with x2gonightly
> builds now will not allow me to connect. When I try I get a pop-up that says:
>
> Connection failed. /usr/lib/x2go/x2gogetrandomport: line 106:
> get_random_port
* On 01/10/2018 04:13 PM, Andrew Munn wrote:
> I'm seeing this situation again. I can see the session in the client as
> usual by when I click on it nothing happens. I think someone in another
> thread mentioned running out of available ports as a possible cause. Is
> that right? What's the s
* On 12/26/2017 02:06 AM, Robert Dinse wrote:
> I see that you pushed another update today on Christmas. Things still
> seem work but I am curious about arguments to nxagent:
>
> root 13298 6.0 0.0 282796 81308 ?S17:02 0:02 nxagent
> -nolisten tcp -nolisten tcp -dpi 96
* On 12/24/2017 06:42 AM, Robert Dinse wrote:
> Just installed the updates and that did fix the issue. Thank you!
Great, at least we've got that.
The new architecture still is a bit weird in that it deletes all RandR modes but
the one that was detected on the remote (i.e., client-side) scr
* On 12/24/2017 04:38 AM, Robert Dinse wrote:
> I applied to a machine that was definitely broken, logged out and logged
> back in and things work with that added argument.
If you're still doing stuff in, say, an hour from now, go for a sync and update
the system at that time. Remove the -rr
* On 12/24/2017 04:19 AM, Robert Dinse wrote:
> That could be, can you shoot me that option one more time, I
> accidentally
> deleted your e-mail, I found machines that are still broke and they have
> different versions of the libs than the ones that are working.
-rrxinerama to disable Xine
* On 12/24/2017 03:45 AM, Robert Dinse wrote:
> It about 99.99% works, one behavior that is still off is if I have
> Window
> Snapping enabled in Mate Tweak (I normally don't so this particular bug does
> not cause me any problems), when it's in a corner a Mate terminal only expands
> to hav
* On 12/24/2017 03:18 AM, Robert Dinse wrote:
> I had built the libs from source but perhaps the repository version
> overwrote them.
Maybe.
In any case, if you specify "-rrxinerama" (mind the spelling and single dash at
the beginning) in /etc/x2go/x2goagent.options, can you confirm that it
* On 12/24/2017 02:02 AM, Robert Dinse wrote:
>What I am trying to say is the behavior changed from a working to
> non-working state without my having changed nx-libs on this end, I only
> changed them after things broke.
Huh, that would be weird. nx-libs changed in the nightly repository
* On 12/24/2017 12:56 AM, Robert Dinse wrote:
> But this went from working to not working after an upgrade of x2go, I
> did not recompile the libs until after it broke in an attempt to fix it.
Yes...? Where's the "but" coming from? Did I ever claim otherwise?
It's obvious that the new nx-li
* On 12/23/2017 09:04 AM, Robert Dinse wrote:
> Ok, I just tried it with lxde, and with lxde display 1 works properly.
> With the new libs the nightly build worked properly until a few days ago when
> there were updates to many of the x2go components. So there is an aspect
> specific to M
* On 12/22/2017 08:08 PM, Mihai Moldovan wrote:
> What does "but I can't use the bottom half or approximately right third of my
> desktop now" mean exactly? Are these regions not drawn at all? Or are they
> drawn
> but insensitive to clicks? Is the window big enoug
* On 12/21/2017 01:13 PM, Robert Dinse wrote:
> I have four machines running 17.10 as servers and a work station running
> Ubuntu 17.10. I have the client set for display 1, so it gives me a full
> screen but I can switch to other things. My monitor is 1920x1080. My client
> version is 4.
* On 12/06/2017 10:55 AM, Robert Dinse wrote:
>
> I am trying to install the nightly build on Mint Sylvia 18.3, but there
> is no 'sylvia' in the repo so I tried to install stretch. I've build the
> nx-libs and installed them without error but attempting to install x2go from
> stretch (18.1
* On 11/27/2017 12:45 PM, Mario Brese wrote:
> is there a time intended to provide the new Client version for Windows?
Sadly, not yet. I can't provide an ETA.
The Windows maintainer has identified problems when connecting via Kerberos
credentials with this new version and intends to fix this issu
* On 11/17/2017 10:34 AM, Mike Gabriel wrote:
> An update version of python(2,3)-wsgilog is available via Debian unstable.
>
> I am currently negotiating with Mihai, who will add that package
> version to our x2go-extras repo area.
For Debian Wheezy, Jessie and Stretch, I have uploaded rebuilt
* On 11/19/2017 11:21 AM, Andrew Munn wrote:
> Yes deleting /tmp/.x2go-$USER did fix it. It happens rarely. I'm not
> sure how long the session runs before this occurs. A fix for this issue
> would be great. Thanks for the suggestion!
Uh, no, my suggestion was *not* to delete this data, it wa
* On 11/18/2017 09:32 AM, Andrew Munn wrote:
> Sometimes x2go works fine. Other times I can't get the session back and
> logs look like this. server version 4.0.1.20. Same results occur when
> connecting from my Windows or Linux client.
Might that be the same problem as described by the other
* On 11/17/2017 09:27 AM, Markus Kuderer wrote:
> Taking a look on the open files (lsof) shows that the session log file
> in /tmp has been deleted meanwhile:
> /tmp/.x2go-lmegast5/C-lmegast5-50-1507636342_stDGNOME_dp32/session.log
> (deleted)
> (background: "old" files in /tmp are deleted automa
* On 11/17/2017 03:52 AM, Robert Dinse wrote:
> I have EDITOR set to /bin/ex and VISUAL set to /bin/vi but apparently
> that is not sufficient in Centos6.
No, because, like I said, both CentOS 6's and 7's sudo packages hard-depend upon
vim-minimal currently.
Mihai
signature.asc
Descrip
* On 11/17/2017 03:24 AM, Jason Heeris wrote:
> If it's anything like Debian, sudo might depend on an editor (*any* editor) so
> that sudoedit works, and vim is just the first one in a dependency OR
> condition.
> Do you have another console editor installed (like Pico, Micro, Emacs)?
Yes, in the
* On 11/17/2017 03:17 AM, Robert Dinse wrote:
> Should be but centos6 is an ancient kludge. I really should move this
> stuff to a modern ubuntu installation.
I've just looked it up. sudo on CentOS 7 depends upon vim-minimal, although a
comment in the ChangeLog mentions "visudo requires vim
* On 11/17/2017 03:13 AM, Robert Dinse wrote:
> On CentOS6, if I remove vim, it removes x2goserver and
> x2goserver-xsession. If I re-install these, it install vim-minimal.
>
> Yum tells me it requires sudo and vim-minimal.
That makes sense. x2goserver does indeed depend upon sudo,
* On 11/17/2017 02:44 AM, Robert Dinse wrote:
> Why does x2goserver on CentOS6 require vim? I delete vim and install
> nvi because I detest the former and prefer the latter. Then x2goserver
> re-installs vim, ARGH.
Our (upstream) x2goserver packages do not depend upon vim.
I've also check
[Resent with correct header, because I messed up myself this time.]
On 11/14/2017 09:35 AM, K. Reinhold Trier wrote:
> thank you, it helped.
Please remember to also include the mailing list when replying.
Okay, good. Watch the DISPLAY number (the first number after the user name in a
session ID.
On 11/13/2017 06:50 PM, K. Reinhold Trier wrote:
> last Thursday after an automatic update of the x2go-server our clients didn't
> receive any more answer from the server.
Yes, X2Go Server 4.0.1.21 was buggy when used with FQDN host names.
> This morning, after an other automatic update of
> the
On 10/17/2017 08:13 AM, Sebastian Turzański wrote:
> Hi
> I still experience this problem
> Can anybody take a look at the debug output (pastebin link below)
> I suspect this can have something to do with x2goclient not generating the
> content of ~./.x2go/etc
> the directory itself is not create
Hi
I will be releasing new stable versions of nx-libs and x2goserver soon.
Due to some file moves between packages, these releases must happen in lock-step
(or more specifically the binary packages built from these releases be available
at the same time).
In order to not potentially break user
Hi
In order to lower resource stress when building packages, I plan to deprecate
support for distributions that have (almost) reached End Of Life on December
31th 2017.
This includes the following distro versions:
- Debian:
o 7.0 "wheezy"
- Fedora
o 23
o 24
o 25
- OpenSuSE
o 13.1
o
On 11/01/2017 11:40 AM, Thomas Porschberg wrote:
> $ps -ef | grep x2go
> root 17045 1 0 11:06 ?00:00:00 /usr/bin/perl
> /usr/sbin/x2gocleansessions
> pberg20099 7153 0 11:11 ?00:00:00 /usr/bin/x2godesktopsharing
>
> My client is a laptop, also running Ubuntu 16.04.
We solved this problem a while ago on IRC.
It boiled down to IPv6 connectivity problems (remote server advertised on
record, on which the ssh daemon wasn't listening) - it wasn't an authentication
failure in the first place. :)
Mihai
signature.asc
Description: OpenPGP digital signature
On 09/24/2017 01:25 AM, Robert Dinse wrote:
> x2go-client versions 4.1.0.0 and 4.1.1.0 both core dump under MacOS X
> 10.7.5 (Lion). 4.0.0.1 does not but also will not login to a non-root account
> on Ubuntu server.
I have no way of reproducing that. We have deprecated 10.7 support and I do
On 10/10/2017 12:13 PM, Mihai Moldovan wrote:
> Whatever sets it, it's not tcsh itself. Likely some global startup script.
> Care
> to grep -R HOSTNAME /etc?
Like I suspected (tested on OpenSUSE Leap 42.3):
/etc/csh.login:
# Remark: /proc/sys/kernel/domainname and the program do
On 10/09/2017 12:44 PM, Frank Steiner wrote:
> I was able to solve this. When I looked into the code, I saw that you
> already to use "bash -c '...'" for all commands, so quoting shouldn't be
> an issue.
I really think it can get problematic easily, for instance with nested single
quotes, that req
On 10/08/2017 12:31 AM, Frank Steiner wrote:
> I see, but that was the latest version the opensuse build repositories offer.
> I'll try to compile form source.
Typically more recent versions are available from our repository, that is
automatically populated with release and nightly builds - but yo
On 10/07/2017 01:07 PM, Frank Steiner wrote:
> we just tried to x2go for the first time (client 4.0.5.2 server 4.0.1
> on SLED 12). It works fine for users with bash as login shell on the
> server side, but fails for those with tcsh.
4.0.5.2 is quite old by now. This said, the change that explicit
On 09/28/2017 01:49 PM, Max A. wrote:
> I'm using a x2go server on CentOS 6.9 (the latest version from EPEL,
> 4.0.1.20), clients use Windows XP/7 and the latest version of X2Go
> Client (4.1.0.0-2017.03.11). Each time the client connects,
> ssh-keygen.exe (C:\Program Files\x2goclient\ssh-keygen
On 09/08/2017 10:31 PM, Robert Kudyba wrote:
> See attached screen shot and suggested commands to run. This is Fedora 26. Any
> ideas?
>
> Name : x2goserver
> Version : 4.0.1.20
> Release : 2.fc26
> Arch : x86_64
> Size : 309 k
> Source : x2goserver-4.0.1.20
On 08/02/2017 06:04 AM, Bruce Ferrell wrote:
> There don't seem to be any right now and as promised, OBS doesn't work.
Yes, there currently aren't OpenSUSE Leap 42.3 builds.
I've already started working on this, should be done in a couple of days.
What exactly did you mean by "as promised"?
Mi
1 - 100 of 248 matches
Mail list logo
