Description of problem: It was running in the background and trying to connect to jabber server. Version-Release number of selected component: sim-0.9.5-0.34.20091129svn3078rev.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: sim crash_function: QObject::connect executable: /usr/bin/sim kernel: 3.15.8-200.mst.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 QObject::connect at kernel/qobject.cpp:1774 #1 QSignal::connect at kernel/qsignal.cpp:153 #2 QSingleShotTimer::start at kernel/qtimer.cpp:281 #3 QTimer::singleShot at kernel/qtimer.cpp:337 #4 SIM::StdResolver::run at sockfactory.cpp:195 #5 QThreadInstance::start at kernel/qthread_unix.cpp:122
Created attachment 927313 [details] File: backtrace
Created attachment 927314 [details] File: cgroup
Created attachment 927315 [details] File: core_backtrace
Created attachment 927316 [details] File: dso_list
Created attachment 927317 [details] File: environ
Created attachment 927318 [details] File: exploitable
Created attachment 927319 [details] File: limits
Created attachment 927320 [details] File: maps
Created attachment 927321 [details] File: open_fds
Created attachment 927322 [details] File: proc_pid_status
Created attachment 927323 [details] File: var_log_messages
How it may be reproduced?
(In reply to Pavel Alexeev (aka Pahan-Hubbitus) from comment #12) > How it may be reproduced? My jabber provider (jabber.cz) was down, unpingeable. After sim start it took approx. 1 hour and the jabber icon was blinking all the time, then it crashed. It was 100% reproducible, I reproduced the crash approx. 4 times. Now my provider is back online and I am unable to reproduce the crash. I tried to change the jabber server in the settings to point to offline machines, but I was unable to reproduce the crash again. I am not sure there is anything helpful in the backtrace.
Sorry, but if it does not reproducible now I'll close it. Thank you for bugreport. If you are be able reproduce it - please reopen.