Bug 1325696

Summary: [abrt] x2goclient: qMalloc(): x2goclient killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Oliver Sampson <oliver>
Component: x2goclientAssignee: Orion Poplawski <orion>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: orion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/82636a8b02cd8c55d056ac4dedfcb693a8330c00
Whiteboard: abrt_hash:505507981dcc88fd932b2cfbc515b3a58a1e5d33;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:47:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Oliver Sampson 2016-04-10 17:49:48 UTC 
Version-Release number of selected component:
x2goclient-4.0.5.1-1.fc22

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/x2goclient
crash_function: qMalloc
executable:     /usr/bin/x2goclient
global_pid:     3280
kernel:         4.4.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 qMalloc at global/qmalloc.cpp:55
 #3 queued_activate at kernel/qobject.cpp:3435
 #4 QMetaObject::activate at kernel/qobject.cpp:3523
 #5 SshMasterConnection::ioErr at moc_sshmasterconnection.cpp:177
 #6 SshMasterConnection::channelLoop at ../src/sshmasterconnection.cpp:1545
 #7 SshMasterConnection::run at ../src/sshmasterconnection.cpp:705
 #8 QThreadPrivate::start at thread/qthread_unix.cpp:352
Comment 1 Oliver Sampson 2016-04-10 17:49:55 UTC 
Created attachment 1145718 [details]
File: backtrace
Comment 2 Oliver Sampson 2016-04-10 17:49:56 UTC 
Created attachment 1145719 [details]
File: cgroup
Comment 3 Oliver Sampson 2016-04-10 17:49:58 UTC 
Created attachment 1145720 [details]
File: core_backtrace
Comment 4 Oliver Sampson 2016-04-10 17:50:00 UTC 
Created attachment 1145721 [details]
File: dso_list
Comment 5 Oliver Sampson 2016-04-10 17:50:01 UTC 
Created attachment 1145722 [details]
File: environ
Comment 6 Oliver Sampson 2016-04-10 17:50:02 UTC 
Created attachment 1145723 [details]
File: limits
Comment 7 Oliver Sampson 2016-04-10 17:50:06 UTC 
Created attachment 1145724 [details]
File: maps
Comment 8 Oliver Sampson 2016-04-10 17:50:07 UTC 
Created attachment 1145725 [details]
File: mountinfo
Comment 9 Oliver Sampson 2016-04-10 17:50:08 UTC 
Created attachment 1145726 [details]
File: namespaces
Comment 10 Oliver Sampson 2016-04-10 17:50:10 UTC 
Created attachment 1145727 [details]
File: open_fds
Comment 11 Oliver Sampson 2016-04-10 17:50:11 UTC 
Created attachment 1145728 [details]
File: proc_pid_status
Comment 12 Oliver Sampson 2016-04-10 17:50:13 UTC 
Created attachment 1145729 [details]
File: var_log_messages
Comment 13 Orion Poplawski 2016-04-11 15:31:29 UTC 
Can you reproduce this crash?

If so, can you run x2goclient under valgrind and get a report from that?
Comment 14 Oliver Sampson 2016-04-11 18:23:48 UTC 
I can't repeat it at will, but I'll see if I can get it to happen again.
Comment 15 Fedora End Of Life 2016-07-19 18:47:50 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.