Multiplying Dbus-daemons forcing restart

[Rick Walker]

Hi Folks,

I'm currently running 3.13.11-100.fc19.x86_64 and have had a problem
with dbus-daemons running amok on this system and even on a few earlier fedora 
revs.

If I do 'ps -ef' I get pages of 

    walker   24457     1  0 15:11 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24475     1  0 15:11 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24493     1  0 15:11 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24511     1  0 15:11 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24529     1  0 15:11 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24547     1  0 15:12 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24565     1  0 15:13 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    walker   24583     1  0 15:13 ?        00:00:00 /bin/dbus-daemon --fork 
--print-pid 5 --print-a
    ...

10) uptime
    15:21:16 up 2 days, 15:15, 13 users,  load average: 0.46, 0.48, 0.49

11) ps -ef | grep dbus-daemon | wc
    103    1434   11738

So, in two days, I've accumulated 103 of these things.

Oh, and if I do a 'killall dbus-daemon' it locks up my desktop. 

I've searched and this seems to have happened to lots of people going
back even into 2012 or so, but I never have seen any definitive
fix.   I'm long past hoping that "the next update" will fix this
problem.

Eventually, things like firefox and exmh will fail with "can't open any
more file descriptors", "no more processes available".  Then I have to
just power cycle and start the inflationary cycle all over again. 

I'm ready to ditch gnome, ditch kde, ditch plasma, or whatever
just to get a system that will stably stay up for more than a
week or so.  Before this happened I could run for a year or more
with no problem.

Any suggestions?
--
Rick Walker