Bug 183870 - Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Summary: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 5
Hardware: All Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-03 09:49 UTC by Radek Vokal
Modified: 2018-04-11 09:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-02 17:23:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Radek Vokal 2006-03-03 09:49:05 UTC
Description of problem:
Evolution eats 100% of my CPU and spams console with

libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoServer raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. yum update to latest rawhide
2. start evolution (3 POP3 accounts, 2 IMAP accounts, apx 10000 email messages) 
Actual results:
spams console, eats CPU

Expected results:
runs smoothly

Additional info:
let me now if you would like to have a backtrace here

Comment 2 John (J5) Palmieri 2007-01-08 19:36:03 UTC
could be an selinux issue.  please attach the output of ps -aux and look to see
if /var/run/dbus/system_bus_socket is there.  Also check in your logs for any
se-linux messages related to D-Bus.  Thanks.  

On a side note evolution should be able to run just fine without the system bus
around.  That should be fixed or filed upstream.

Comment 3 Matthew Miller 2007-04-06 19:21:13 UTC
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.

[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]

Comment 4 Matěj Cepl 2007-08-31 15:22:54 UTC
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report.  If
after a month's time we have not heard back from you, we will have to close this

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.

Comment 5 Matthew Barnes 2007-10-02 17:23:11 UTC

Note You need to log in before you can comment on or make changes to this bug.