Hide Forgot
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
Created attachment 1145718 [details] File: backtrace
Created attachment 1145719 [details] File: cgroup
Created attachment 1145720 [details] File: core_backtrace
Created attachment 1145721 [details] File: dso_list
Created attachment 1145722 [details] File: environ
Created attachment 1145723 [details] File: limits
Created attachment 1145724 [details] File: maps
Created attachment 1145725 [details] File: mountinfo
Created attachment 1145726 [details] File: namespaces
Created attachment 1145727 [details] File: open_fds
Created attachment 1145728 [details] File: proc_pid_status
Created attachment 1145729 [details] File: var_log_messages
Can you reproduce this crash? If so, can you run x2goclient under valgrind and get a report from that?
I can't repeat it at will, but I'll see if I can get it to happen again.
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.