Bug 757073

Summary: [abrt] kdebase-runtime-4.7.3-10.fc16: __GI_raise: Process /usr/bin/kde-open was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Pavel Alexeev <pahan>
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5fe7b8f238732d8a318e67ca48bc448ad1665f1b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-19 15:31:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 746592    
Bug Blocks:    
Attachments:
Description Flags
File: event_log
none
File: environ
none
File: dso_list
none
File: coredump
none
File: smolt_data
none
File: maps
none
File: backtrace none

Description Pavel Alexeev 2011-11-25 12:30:54 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        kde-open /home/pasha/imus/IdeaProjects/imus/ascug-maket/ascug-esb-modules/data/prgmain.ais/md/report_2011-11-25_151134.xls
crash_function: __GI_raise
executable:     /usr/bin/kde-open
kernel:         3.1.1-2.fc16.x86_64
pid:            24387
pwd:            /home/pasha/imus/IdeaProjects/imus/ascug-maket/ascug-esb-modules/data/prgmain.ais/md
reason:         Process /usr/bin/kde-open was killed by signal 6 (SIGABRT)
time:           Пт. 25 нояб. 2011 16:10:43
uid:            1000
username:       pasha
var_log_messages: Nov 25 16:10:43 hubbitus abrt[24388]: Saved core dump of pid 24387 (/usr/bin/kde-open) to /var/spool/abrt/ccpp-2011-11-25-16:10:43-24387 (3809280 bytes)
xsession_errors: 

backtrace:      Text file, 12892 bytes
dso_list:       Text file, 7115 bytes
environ:        Text file, 5814 bytes
event_log:      Binary file, 2285 bytes
maps:           Text file, 32774 bytes
smolt_data:     Binary file, 3698 bytes
Comment 1 Pavel Alexeev 2011-11-25 12:30:59 UTC 
Created attachment 536214 [details]
File: event_log
Comment 2 Pavel Alexeev 2011-11-25 12:31:01 UTC 
Created attachment 536215 [details]
File: environ
Comment 3 Pavel Alexeev 2011-11-25 12:31:03 UTC 
Created attachment 536216 [details]
File: dso_list
Comment 4 Pavel Alexeev 2011-11-25 12:31:18 UTC 
Created attachment 536217 [details]
File: coredump
Comment 5 Pavel Alexeev 2011-11-25 12:31:20 UTC 
Created attachment 536218 [details]
File: smolt_data
Comment 6 Pavel Alexeev 2011-11-25 12:31:22 UTC 
Created attachment 536219 [details]
File: maps
Comment 7 Pavel Alexeev 2011-11-25 12:31:24 UTC 
Created attachment 536220 [details]
File: backtrace
Comment 8 Rex Dieter 2011-11-25 15:10:22 UTC 
*** Bug 757074 has been marked as a duplicate of this bug. ***
Comment 9 Kevin Kofler 2011-11-25 17:18:06 UTC 
This trips on this kFatal in kioclient.cpp:
    if (!QDBusConnection::sessionBus().isConnected())
        kFatal(101) << "Session bus not found" ;

Your D-Bus is not working, check your configuration. We can't do anything about this in kdebase-runtime.
Comment 10 Pavel Alexeev 2011-12-11 15:41:11 UTC 
And what I should check in configuration? Is D-Bus service must be runned by dewfault and application crash is not "future" instead of bug??
Comment 11 Kevin Kofler 2011-12-11 17:27:20 UTC 
It works for everyone else. Something's wrong on your system.
Comment 12 Pavel Alexeev 2011-12-12 15:45:16 UTC 
May be, may be. In any case, even if there some of misconfiguration present crash is not user-friendly error processing, how you think?
Comment 13 Rex Dieter 2011-12-12 16:00:53 UTC 
If dbus isn't working, there's not much else to do frankly.  It's akin to basic stuff like kernel(drivers)
Comment 14 Rex Dieter 2011-12-12 16:03:42 UTC 
You're free to check if dbus is running,
ps aux | grep dbus
you should see 2 , one session bus owned by "dbus" user, and one by you.  X (or /usr/bin/startkde) starts the latter via dbus-launch command.  See /usr/bin/startkde on how it gets launched, and the basic error it reports if one cannot connect to it.
Comment 15 Pavel Alexeev 2011-12-19 10:03:58 UTC 
After some updates it seams working now for me. Please note - no any changes in configuration was made.
Comment 16 Kevin Kofler 2011-12-19 15:31:26 UTC 
Not reproducible, closing.