Bug 885688

Summary: [abrt] kde-runtime-drkonqi-4.9.90-1.fc18: qt_message_output: Process /usr/libexec/kde4/drkonqi was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Fl@sh <alex.mail.1534>
Component: kde-runtimeAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jreznik, kevin, ltinkl, paulbarbee, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5d229539bf5c96f37539bc6ba11422bf067d5da2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 23:26:39 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: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Fl@sh 2012-12-10 12:28:14 UTC 
Version-Release number of selected component:
kde-runtime-drkonqi-4.9.90-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/kde4/drkonqi -display :0 --appname kactivitymanagerd --apppath /usr/bin --signal 11 --pid 1695 --appversion 3.0 --programname '\xd0\x94\xd0\xb8\xd1\x81\xd0\xbf\xd0\xb5\xd1\x82\xd1\x87\xd0\xb5\xd1\x80 \xd0\xba\xd0\xbe\xd0\xbc\xd0\xbd\xd0\xb0\xd1\x82 KDE' --bugaddress submit.org --startupid localhost.localdomain;1355133752;955960;1643_TIME0 --restarted
crash_function: qt_message_output
executable:     /usr/libexec/kde4/drkonqi
kernel:         3.6.9-4.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Dec 10 15:10:55 localhost abrt[2561]: Saved core dump of pid 2559 (/usr/libexec/kde4/drkonqi) to /var/spool/abrt/ccpp-2012-12-10-15:10:54-2559 (8671232 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 qt_message_output at global/qglobal.cpp:2323
 #3 QDebug::~QDebug() at /lib64/libkdeui.so.5
 #4 KApplicationPrivate::init(bool) at /lib64/libkdeui.so.5
 #5 KApplication::KApplication(bool) at /lib64/libkdeui.so.5
Comment 1 Fl@sh 2012-12-10 12:28:20 UTC 
Created attachment 660784 [details]
File: backtrace
Comment 2 Fl@sh 2012-12-10 12:28:23 UTC 
Created attachment 660785 [details]
File: build_ids
Comment 3 Fl@sh 2012-12-10 12:28:25 UTC 
Created attachment 660786 [details]
File: cgroup
Comment 4 Fl@sh 2012-12-10 12:28:28 UTC 
Created attachment 660787 [details]
File: core_backtrace
Comment 5 Fl@sh 2012-12-10 12:28:31 UTC 
Created attachment 660788 [details]
File: dso_list
Comment 6 Fl@sh 2012-12-10 12:28:34 UTC 
Created attachment 660789 [details]
File: environ
Comment 7 Fl@sh 2012-12-10 12:28:39 UTC 
Created attachment 660790 [details]
File: limits
Comment 8 Fl@sh 2012-12-10 12:28:42 UTC 
Created attachment 660791 [details]
File: maps
Comment 9 Fl@sh 2012-12-10 12:28:46 UTC 
Created attachment 660792 [details]
File: open_fds
Comment 10 Fl@sh 2012-12-10 12:28:50 UTC 
Created attachment 660793 [details]
File: proc_pid_status
Comment 11 Paul Barbee 2013-02-14 18:35:19 UTC 
started Kde 4.10 and kde-runtime was reported as crashed. There were no other signs of a crash of the main DE runtime, such as other related oprograms or the UI failing to respond.

backtrace_rating: 4
cmdline:        /usr/libexec/kde4/drkonqi -display :0 --appname kactivitymanagerd --apppath /usr/bin --signal 11 --pid 30073 --appversion 3.0 --programname 'KDE Activity Manager' --bugaddress submit.org --startupid paul-linux;1360789379;813173;30065_TIME0 --restarted
crash_function: qt_message_output
executable:     /usr/libexec/kde4/drkonqi
kernel:         3.7.6-201.fc18.x86_64
package:        kde-runtime-drkonqi-4.10.0-2.fc18
reason:         Process /usr/libexec/kde4/drkonqi was killed by signal 6 (SIGABRT)
remote_result:  NOTFOUND
uid:            1000
Comment 12 Than Ngo 2013-02-28 10:04:30 UTC 
i cannot reproduce the crash with latest 4.10 on f18 with following steps: 


1) start kwrite
2) killall -SIGABRT kwrite

drkonqi startet without any crash!


could you please try above steps and see if drkonqi crashes?

thanks
Comment 13 Kevin Kofler 2013-02-28 23:26:39 UTC 
This looks like the same crash as bug #873520.

*** This bug has been marked as a duplicate of bug 873520 ***