Mailinglist Archive: opensuse-kde (38 mails)
| < Previous | Next > |
[opensuse-kde] Re: RESOLVED dbus-daemon crashes with SIGSEGV after update to KDE 3.5.6
- From: Boyan Tabakov <blade.alslayer@xxxxxxxxx>
- Date: Sat, 27 Jan 2007 13:20:13 +0200
- Message-id: <200701271320.18174.blade.alslayer@xxxxxxxxx>
On 27.1.2007 00:37:54 Boyan Tabakov wrote:
> 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?
--
Blade hails you...
Farewell - no words to say
Beside the cross on your grave
And those forever burning candles
--Nightwish
> 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?
--
Blade hails you...
Farewell - no words to say
Beside the cross on your grave
And those forever burning candles
--Nightwish
| < Previous | Next > |