On Sun, 2007-01-28 at 12:17 -0500, Patrick Shanahan wrote: > * Scott Barninger <[EMAIL PROTECTED]> [01-28-07 12:08]: > > I've searched the list archives as well as a general google search > > but can find no references to this problem. My 10.1 installation > > recently started failing to start the dbus-daemon with a segmentation > > fault on boot. Checking status shows it running but it is dead, and > > gnome power manager refuses to start, giving a warning message when > > logging in to the desktop. Attempting a restart just indicates a > > segfault again. > > from opensuse-kde list (partial quote): > > From: Boyan Tabakov <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [opensuse-kde] Re: RESOLVED dbus-daemon crashes with SIGSEGV > after update to KDE 3.5.6 > Date: Sat, 27 Jan 2007 13:20:13 +0200 > References: <[EMAIL PROTECTED]> > In-Reply-To: <[EMAIL PROTECTED]> > Precedence: bulk > Message-Id: <[EMAIL PROTECTED]> > > > Hi, > > Unfortunately my today's update to KDE 3.5.6 got me surprised with > > something: d-bus daemon fails to start due to segmentation fault. > > > > Nothing appears in the /var/log/messages log. > > > > First I noticed that my unmounted optical drives icons appeared on > > the desktop, which they previously did, only when a medium is > > inserted. > > > > Then I got some messages about HAL being needed to mount those. So > > why wasn't hal running - answer - dbus could not start. > > > > I wish, I saved my update log... Anyway, I am pretty sure that the > > update was only on the normal kde stuff - all the kde* packages, qt, > > arts and some other that usually get updated upon new KDE release. > > > > Reinstalling dbus-1 or the kde 3.5.6 packages showed no results. > > > > Any ideas? > > After some debugging the problem revealed itself. > > This was caused by this bug in dbus-userdb.c sourse file: > > http://lists.freedesktop.org/archives/dbus/2006-February/004278.html > > An infinite recursion is caused by having some group name in the config > files that does not actually exists on the system. In my case this > seemed to be 'netdev', mentioned in avahi-dbus.conf. This file has been > created two days ago, during my previous update. > > The quick workaround is to create a dummy group 'netdev'. > > Maybe SuSE should release a patched version of dbus? >
Thanks, that did the trick. Curious that my searches both on opensuse lists and a general google failed to find that, I guess it's too new to get indexed. Thanks again. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
