Re: Trouble by last dbus patch (46e6c3fa8034b12d178d605f3f5d7efe69671a13)?

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2011-10-27 at 22:30 +0200, Andreas Müller wrote:
> Since the last updates of all layers (angstrom based) I have issues with
> 
> * networkmanager/nm-applet (meta-oe): I am not allowed to change the settings
>   any more
> * xfce-session (meta-oe): Logging out takes very long and Restart/Shutdown is 
>   disabled
> 
> I remember that I had similar issues a while ago. That could be worked around
> by starting some dbus stuff ( do not exactly remember what it was ).
> 
> With this vague idea I checked and found in oe-core:
> 
> | dbus: use useradd class to allow use in read-only filesystems
> | author	Otavio Salvador <otavio@ossystems.com.br>
> | commit	46e6c3fa8034b12d178d605f3f5d7efe69671a13
> 
> Not understanding totally what is all about I see in /etc/passw
> 
> | messagebus:x:999:998::/var/lib/dbus:/bin/sh
> 
> but I don't have /var/lib/dbus on my sytem!!
> 
> I did not check yet, but maybe this is an incompatibilty with angstrom custom
> 
> | FILESYSTEM_PERMS_TABLES = "fs-perms-angstrom.txt"
> 
> somebody around to enlight the darkness?

There are some issues due to the orcering of when we now start some of
the services. After the above change the dbus service starts much
earlier on first boot, before some of the other postinstalls have run.
This can mean you see errors due to users which have not yet been
created by postinstalls (e.g. avahi or xuser) yet the dbus files
reference these and its trying to start those services.

We're looking at fixing the remaining adduser type postinstalls to
address this. I'm not sure if this is related to the problem you were
seeing above or not.

Cheers,

Richard