X2Go Bug report logs - #44
Segmentation Violation in ONMainWindow::slotProxyFinished(

[Message part 1 (text/plain, inline)]
Package: x2goclient
Version: X2GoClient V. 3.99.3.0 (Qt - 4.8.2)
Severity: important

Dear maintainer,

I have compiled git version origin/master of x2goclient on a vanilla Debian Wheezy i386.

Connecting to a SSH server creates an error signal 11 (SIGSEGV) for illegally accessing memory.

I ran x2goclient again with valgrind. Please, find the output in the appendix.

Best regards

Heirnich Schuchardt

[output.txt (text/plain, attachment)]
[Message part 1 (text/plain, inline)]
Am 30.09.2012 10:26, schrieb glpk xypron:
> Package: x2goclient
> Version: X2GoClient V. 3.99.3.0 (Qt - 4.8.2)
> Severity: important
> 
> Dear maintainer,
> 
> I have compiled git version origin/master of x2goclient on a vanilla Debian Wheezy i386.
> 
> Connecting to a SSH server creates an error signal 11 (SIGSEGV) for illegally accessing memory.
> 
> I ran x2goclient again with valgrind. Please, find the output in the appendix.
> 
> Best regards
> 
> Heirnich Schuchardt
> 
> 
> 
> _______________________________________________
> X2Go-Dev mailing list
> X2Go-Dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/x2go-dev

Hello Heirnich,

I made a lot of changes in SSH classes today:

http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ef8c9486314e87bf6aeb748b46b1c35f1b975213

I think, that should solve problem, that you described.

Regards,
Alex
-- 
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email:  oleksandr.shneyder@obviously-nice.de
web: www.obviously-nice.de

--> X2go - everywhere@home

[signature.asc (application/pgp-signature, attachment)]
[Message part 1 (text/plain, inline)]
Hi Heinrich,

On Mo 01 Okt 2012 16:11:54 CEST Oleksandr Shneyder wrote:

> Am 30.09.2012 10:26, schrieb glpk xypron:
>>
>> Dear maintainer,
>>
>> I have compiled git version origin/master of x2goclient on a  
>> vanilla Debian Wheezy i386.
>>
>> Connecting to a SSH server creates an error signal 11 (SIGSEGV) for  
>> illegally accessing memory.
>>
>> I ran x2goclient again with valgrind. Please, find the output in  
>> the appendix.
>>
>> Best regards
>>
>> Heirnich Schuchardt
>
> Hello Heirnich,
>
> I made a lot of changes in SSH classes today:
>
> http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ef8c9486314e87bf6aeb748b46b1c35f1b975213
>
> I think, that should solve problem, that you described.
>

Can you please verify that the issue you reported is gone and--if  
so--send a mail to

"""
To: control@bugs.x2go.org
Subject: (none)
Body:
 tags #44 pending
 thanks
"""

That would be awesome!!!
Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]
[Message part 1 (text/plain, inline)]
Dear Mike,

thank for informing me about the updates in the git repository.
I still see the segmentation violation. See appendix.

Best regards

Heinrich

[output.txt (text/plain, attachment)]
[Message part 1 (text/plain, inline)]
Hi,
I think, I experienced this bug as well (same kind of backtrace). In my
case this happened, when installing nxproxy and x2goclient in a non
standard place which is not on the path.
The client tries to start nxproxy which fails. x2goclient never checks, if
the start suceeded or not (see x2goclient-4.0.0.1/onmainwindow.cpp, lines:
3135, 5065).
Workaround: add nxproxy to $PATH.

Best,
Lukas

[Message part 2 (text/html, inline)]

X2Go Bug report logs - #44 Segmentation Violation in ONMainWindow::slotProxyFinished(

X2Go Bug report logs - #44
Segmentation Violation in ONMainWindow::slotProxyFinished(