Description of problem: Apper did not gracefully handle an already existing yum update session. Version-Release number of selected component: apper-0.7.2-4.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/libexec/kde4/apper-sentinel crash_function: qt_message_output kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (6 frames) : #2 qt_message_output at global/qglobal.cpp:2323 : #3 qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) at global/qglobal.cpp:2369 : #4 qFatal at global/qglobal.cpp:2552 : #5 QObjectPrivate::QObjectPrivate at kernel/qobject.cpp:138 : #6 ~QString at ../../src/corelib/tools/qstring.h:880 : #7 QKeyMapperPrivate::translateKeyEvent at kernel/qkeymapper_x11.cpp:1805
Created attachment 663747 [details] File: core_backtrace
Created attachment 663748 [details] File: environ
Created attachment 663749 [details] File: limits
Created attachment 663750 [details] File: backtrace
Created attachment 663751 [details] File: cgroup
Created attachment 663752 [details] File: smolt_data
Created attachment 663753 [details] File: executable
Created attachment 663754 [details] File: maps
Created attachment 663755 [details] File: dso_list
Created attachment 663756 [details] File: proc_pid_status
Created attachment 663757 [details] File: open_fds
Created attachment 663758 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 887133 ***