Re: Latest dbus update may hang kde4 in NetBSD amd64

[Sverre Froyen <sverre%viewmark.com@localhost>]

On Friday 03 August 2012 10:14:26 David Brownlee wrote:
> On 2 August 2012 15:17, David Shao <davshao%gmail.com@localhost> wrote:
> > After the latest pkgsrc current updates, of which I believe dbus to be
> > the most likely culprit, kde4 hangs on the splash screen with near
> > 100% CPU usage by a kdeinit4 process.  This occurs on two NetBSD
> > 6.99.10 amd64 machines, one Intel, one AMD, using Radeon 4xxx graphics
> > cards.
> > 
> > I do not enable hal anymore because it was cause filesystem corruption
> > to the extent of requiring a fsck, but I enable dbus and famd.
> > 
> > On the bright side, at least xfce4 now allows Terminal usage for both
> > machines without freezing.
> 
> Just a datapoint - similar kde4 behaviour here - NetBSD/amd64 netbsd-6
> from Aug 1, very latest pkgsrc compiled yesterday. Hangs after
> displaying the second splash icon (crossed spanner & screwdriver).
> 
> Tested with hal & dbus on in rc.conf and off (killed). Behaviour unchanged.
> 
> ps shows:
> abs    10380 86.1  0.5 398344  38288 ?      Ol    5:06PM 0:39.96
> kdeinit4: kdeinit4: kdeinit4: kded4

I'm seeing the same thing after an "make replace" in sysutils/dbus. A ktrace 
of the kded4 process shows a stream of

   205      1 kdeinit4 CALL  poll(0x7f7fffffa2d0,1,0xfffeb2c8)
   205      1 kdeinit4 RET   poll -1 errno 22 Invalid argument
   205      1 kdeinit4 CALL  __gettimeofday50(0x7f7fffffa340,0)
   205      1 kdeinit4 RET   __gettimeofday50 0

calls. Killing kded4 makes the startup continue. After the desktop appears, I 
see high CPU usage for kwalletd and kopete (perhaps because kded4 is no longer 
running). Killing and restarting appear to produce a normal system. No idea 
why. This is on amd64 with dbus and hal set to on in rc.conf.

Regards,
Sverre