Control: close -1
On So 03 Mai 2015 23:03:33 CEST, Mihai Moldovan wrote:
Package: packages.x2go.org
The current version of createrepo leaves trash behind in /tmp/ every
time it is
executed.
The most recent version in Debian unstable should fix this problem and be
trivially installable
On Thu, Apr 30, 2015 at 11:35 AM, Michael DePaulo mikedep...@gmail.com wrote:
Sent from my Android Smartphone
-- Forwarded message --
From: Andreas Schneider a...@cryptomilk.org
Date: Apr 30, 2015 10:33 AM
Subject: libssh 0.6.5 has been released to address CVE-2015-3146
To:
Processing control commands:
reopen -1 =
Bug #845 {Done: Stefan Baur x2go-m...@baur-itcs.de} [x2goclient] Windows
client missing language changing option
Bug reopened
Ignoring request to alter fixed versions of bug #845 to the same values
previously set
tags -1 - not-a-bug wontfix
Bug #845
tag #845 pending
fixed #845 4.0.4.0
thanks
Hello,
X2Go issue #845 (src:x2goclient) reported by you has been
fixed in X2Go Git. You can see the changelog below, and you can
check the diff of the fix at:
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=fc224ac
The issue will most
Package: nx-libs
Version: 3.5.0.29
#0 GetULONG (buffer=buffer@entry=0x31ff000 error: Cannot access memory at
address 0x31ff000, bigEndian=0) at Misc.cpp:518
518 return *((unsigned int *) buffer);
Thread 1 (Thread 0x7fae35376740 (LWP 4320)):
#0 GetULONG (buffer=buffer@entry=0x31ff000
On 05.05.2015 02:25 AM, Real, Elizabeth (392K) wrote:
I keep getting the same error: protocol mismatch, this
http://wiki.x2go.org/doku.php/wiki:advanced:authentication:passwordless-ssh
is not working. Can you send me other documentation you may have?
Uhm, no, I don't mean client SSH keys.
On 04.05.2015 11:58 PM, Stefan Baur wrote:
This is the error I get on the client: x2go-ERROR-2 Connection
Error(Can not connect to 128.149.23.102:22): Protocol mismatch:
Protocol mismatch doesn't sound like something X2Go-specific.
It might be half-X2Go-specific.
Please make sure that at
On 04.05.2015 07:11 PM, Mihai Moldovan wrote:
Hmm, OK, that looks alright. It's a bug indeed. Triggered by Qt 4.8.x, but
still.
Thanks for going down that road with me!
Please fetch
