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
Created attachment 536214 [details] File: event_log
Created attachment 536215 [details] File: environ
Created attachment 536216 [details] File: dso_list
Created attachment 536217 [details] File: coredump
Created attachment 536218 [details] File: smolt_data
Created attachment 536219 [details] File: maps
Created attachment 536220 [details] File: backtrace
*** Bug 757074 has been marked as a duplicate of this bug. ***
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.
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??
It works for everyone else. Something's wrong on your system.
May be, may be. In any case, even if there some of misconfiguration present crash is not user-friendly error processing, how you think?
If dbus isn't working, there's not much else to do frankly. It's akin to basic stuff like kernel(drivers)
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.
After some updates it seams working now for me. Please note - no any changes in configuration was made.
Not reproducible, closing.