On Wed, 2003-10-15 at 11:52, David Zeuthen wrote: > with current d-bus head an application can make the system message bus, > dbus-daemon-1, occupy 100% CPU and not respond. Can you get a backtrace of where it's stuck? Or track down further the exact ChangeLog that broke it? (clearly mine of course) Havoc