X2Go Bug report logs - #651
x2goclient segfault on update to 4.0.3 on ubuntu 14.04

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Rob Izzard <rob.izzard@gmail.com>

Date: Thu, 23 Oct 2014 07:20:02 UTC

Severity: normal

Found in version 4.0.3

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#651: [X2Go-Dev] x2goclient segfault on update to 4.0.3 on ubuntu 14.04
Reply-To: Mihai Moldovan <ionic@ionic.de>, 651@bugs.x2go.org
Resent-From: Mihai Moldovan <ionic@ionic.de>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Wed, 15 Nov 2017 19:20:01 +0000
Resent-Message-ID: <handler.651.B651.151077350910800@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 651
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 651-submit@bugs.x2go.org id=B651.151077350910800
          (code B ref 651); Wed, 15 Nov 2017 19:20:01 +0000
Received: (at 651) by bugs.x2go.org; 15 Nov 2017 19:18:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: *
X-Spam-Status: No, score=1.5 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,RDNS_NONE autolearn=no autolearn_force=no
	version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 3F2B95DACF
	for <651@bugs.x2go.org>; Wed, 15 Nov 2017 20:18:05 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p13Gs6k6cthU for <651@bugs.x2go.org>;
	Wed, 15 Nov 2017 20:18:00 +0100 (CET)
Received: from mail.ionic.de (unknown [IPv6:2001:41d0:a:588b:1::2])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 203D85DA2B
	for <651@bugs.x2go.org>; Wed, 15 Nov 2017 20:18:00 +0100 (CET)
Received: from [10.30.44.7] (178.162.222.41.adsl.inet-telecom.org [178.162.222.41])
	by mail.ionic.de (Postfix) with ESMTPSA id 850734F0068F;
	Wed, 15 Nov 2017 20:17:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ionic.de; s=default;
	t=1510773479; bh=JNAR3QWN6HSxlumL0LRgALr/RZWmFWuNybpuh2v5gCg=;
	h=Subject:To:References:From:Date:In-Reply-To:From;
	b=rGq4+AsGNRoCyRr35M9D3Qjuxf26fCj5TwMx5Xxb+L1pM/HDjO6D3YxHqgouJ9qo8
	 vEbzdk6YDNCpOtWLvpE3gVruaMkC+lXjJu2jSLS1j5qlxrVY+n1vXpZzcaBilnjRSz
	 6vyEDeddt1D20tbplVkyJQiso2cUSta8xwFHipAM=
To: Rob Izzard <rob.izzard@gmail.com>, 651@bugs.x2go.org
References: <CANcHt4Qon_cfpmdV8YHo9SZ5uTfWKs-QCCorxnnWk_X0KbAfcQ@mail.gmail.com>
 <c4a63b85-5858-dd31-2191-63aece78d6b0@ionic.de>
 <CANcHt4T96YD6r45C5Q+r-5OfbQ0pcm1MGtGcuwqhSAhhSRtEhg@mail.gmail.com>
From: Mihai Moldovan <ionic@ionic.de>
Message-ID: <08d92434-c52a-9233-b2d0-93a3134d7d47@ionic.de>
Date: Wed, 15 Nov 2017 20:17:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CANcHt4T96YD6r45C5Q+r-5OfbQ0pcm1MGtGcuwqhSAhhSRtEhg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="kf8EFxGtvmPdVgoEFl6HHPr0jVPj6T4b1"

[Message part 1 (text/plain, inline)]
* On 11/15/2017 09:29 AM, Rob Izzard wrote:
> wow, this was a long time ago :)

Yeah, I went through some old bug reports. Sometimes they are still valid but
require more input, other times they either look like duplicates or like reports
that were fixed meanwhile - but never marked as such.

And of course people stop using the software or using special-purpose mail
addresses that won't be checked again, so getting a response is difficult at times.


> I haven't had a crash, freeze or lost a desktop for a while (6
> months?). That's not to say it won't happen again :) but it's been
> going well lately, thanks to the great effort by you guys.

Yeah, but that's probably a side effect of connecting to another machine, or
updating it, or plainly reinstalling it.

As far as I can tell, this bug report is still valid. X2Go Client doesn't handle
server-side errors as well as it could.

A way to reproduce this would be great, but I guess I could just make it fail
and test manually.


What probably happened in your case is that you updated a release version of
x2goserver to the nightly version - but the database schema upgrade didn't work
correctly for some reason.



Mihai


[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:44:23 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.