Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Jun 2008 12:21:36 -0400
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        jahnke@sonatabio.com
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: Gnome 2.22: Daemons gone wild
Message-ID:  <1213978896.38700.9.camel@shumai.marcuscom.com>
In-Reply-To: <1213806747.4251.10.camel@pinot.fmjassoc.com>
References:  <1213806747.4251.10.camel@pinot.fmjassoc.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-98StTBUOLyq46vwWg2xy
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2008-06-18 at 09:32 -0700, Frank Jahnke wrote:
> I have had substantial problems with Gnome-related daemons and processes
> misbehaving since the gettext upgrade and Gnome version bump.  Before
> that everything worked as it should.  Now things are wild, and it does
> not matter whether I start things using gnome_enable or the individual
> daemons in /etc/rc.conf.
>=20
> hald no longer starts, but does so from the command line.  trackerd
> starts, and it should not (I usually have to kill trackerd three or four
> times before it gives up).  bonobo on start-up consumes one of my two
> CPUs.  pdftotex starts for some unknown reason, and it too consumes one
> CPU and must be killed a couple of times before it stays in its grave.

Hald has a special startup script which causes it to spin waiting for
the gettys to be started.  When it detects they are running, then it
starts up.  This loop will only last 60 seconds.  So, if it takes longer
than 60 seconds between when hald is started and init is run, then hald
will not come up at boot time.  You can edit the hald script, and change
line 69 to make the number of loop iterations longer, or figure out why
your system is being so slow.

Bonobo-activation-server should not be CPU intensive at all.  You might
try ktrace'ing it to find out what it is doing.  I don't use tracker or
pdftotex, so I can't comment on them.

>=20
> Adding the clock to the top panel causes is unsuccessful, though adding
> it after gnome loads works on the second try (the first attempt also
> crashes).  Sometimes that audio volume loads; sometimes it does not.

I have been looking at this for a while.
Edit /usr/local/share/PolicyKit/policy/org.gnome.clockapplet.mechanism.poli=
cy, and remove all of the localized lines (those with xml:LANG).  See if th=
at helps.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-98StTBUOLyq46vwWg2xy
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkhb2Q8ACgkQb2iPiv4Uz4e9FACgpv7AgIqVr/sIAzQgB6wTx4HB
rqkAn0gOyKvepwSLttY4dpwkmL6AS2rH
=4i9N
-----END PGP SIGNATURE-----

--=-98StTBUOLyq46vwWg2xy--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1213978896.38700.9.camel>