Bug 1186025

Summary: [abrt] x2goclient: QProcess::terminate(): x2goclient killed by SIGSEGV
Product: [Fedora] Fedora Reporter: christopher.bollinger
Component: x2goclientAssignee: Orion Poplawski <orion>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: darthludi, orion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2e82538dbfc867bdfcc99326abff4b294d745e18
Whiteboard: abrt_hash:fde96253a09aeb081757dffffd0d8742e1ce4cc4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:21:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description christopher.bollinger 2015-01-26 20:43:59 UTC
Description of problem:
Problem occurred upon breaking a connection.  I closed the window showing my remote X display using the 'X' at the top right of the window.

Version-Release number of selected component:
x2goclient-4.0.3.1-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        x2goclient
crash_function: QProcess::terminate
executable:     /usr/bin/x2goclient
kernel:         3.17.8-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 QProcess::terminate at io/qprocess.cpp:2112
 #1 ONMainWindow::termSession at ../onmainwindow.cpp:5952
 #2 ONMainWindow::slotTermSessFromSt at ../onmainwindow.cpp:4573
 #3 ONMainWindow::qt_static_metacall at moc_onmainwindow.cpp:366
 #4 QMetaObject::activate at kernel/qobject.cpp:3567
 #5 QAbstractButton::clicked at .moc/release-shared/moc_qabstractbutton.cpp:219
 #6 QAbstractButtonPrivate::emitClicked at widgets/qabstractbutton.cpp:548
 #7 QAbstractButtonPrivate::click at widgets/qabstractbutton.cpp:541
 #8 QAbstractButton::mouseReleaseEvent at widgets/qabstractbutton.cpp:1123
 #9 QToolButton::mouseReleaseEvent at widgets/qtoolbutton.cpp:723

Comment 1 christopher.bollinger 2015-01-26 20:44:01 UTC
Created attachment 984395 [details]
File: backtrace

Comment 2 christopher.bollinger 2015-01-26 20:44:01 UTC
Created attachment 984396 [details]
File: cgroup

Comment 3 christopher.bollinger 2015-01-26 20:44:02 UTC
Created attachment 984397 [details]
File: core_backtrace

Comment 4 christopher.bollinger 2015-01-26 20:44:03 UTC
Created attachment 984398 [details]
File: dso_list

Comment 5 christopher.bollinger 2015-01-26 20:44:03 UTC
Created attachment 984399 [details]
File: environ

Comment 6 christopher.bollinger 2015-01-26 20:44:04 UTC
Created attachment 984400 [details]
File: exploitable

Comment 7 christopher.bollinger 2015-01-26 20:44:05 UTC
Created attachment 984401 [details]
File: limits

Comment 8 christopher.bollinger 2015-01-26 20:44:06 UTC
Created attachment 984402 [details]
File: maps

Comment 9 christopher.bollinger 2015-01-26 20:44:06 UTC
Created attachment 984403 [details]
File: open_fds

Comment 10 christopher.bollinger 2015-01-26 20:44:07 UTC
Created attachment 984404 [details]
File: proc_pid_status

Comment 11 christopher.bollinger 2015-01-26 20:44:08 UTC
Created attachment 984405 [details]
File: var_log_messages

Comment 12 Orion Poplawski 2015-01-26 23:02:15 UTC
#0  QProcess::terminate (this=0x0) at io/qprocess.cpp:2112
        d = <error reading variable d (Cannot access memory at address 0x8)>
#1  0x00000000004616b0 in ONMainWindow::termSession (this=this@entry=0x17a9ff0, sessId=..., warn=warn@entry=false) at ../onmainwindow.cpp:5952

    if ( shadowSession )
    {
        nxproxy->terminate();  <---
        return true;
    }

Looks like nxproxy may be null at this point, or shortly thereafter.

Looks like: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=761

any chance you hit the terminate button twice?

Comment 13 Orion Poplawski 2015-05-11 15:20:37 UTC
*** Bug 1220267 has been marked as a duplicate of this bug. ***

Comment 14 Fedora End Of Life 2015-05-29 13:38:10 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-06-30 01:21:22 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.