Adam Williamson awilliam at redhat.com
Fri Nov 5 23:46:42 UTC 2010

On Fri, 2010-11-05 at 19:31 -0400, Richard Ryniker wrote:
> Adam Williamson <awilliam at redhat.com> wrote:
>   It fails in this particular way because you don't have NM even
>   installed
> I don't?  This was a straightforward installation from the F14
> installation DVD, updated to the current date.  I see:

oh, sorry, I was working off memory, I thought you said you didn't have
it installed.

>   [ryniker at mini ~]$ rpm -q --all | grep Network
>   NetworkManager-0.8.1-9.git20100831.fc14.i686
>   NetworkManager-openconnect-0.8.1-1.fc14.i686
>   NetworkManager-glib-0.8.1-9.git20100831.fc14.i686
>   NetworkManager-vpnc-0.8.1-1.fc14.i686
>   NetworkManager-gnome-0.8.1-9.git20100831.fc14.i686
>   NetworkManager-pptp-0.8.1-1.fc14.i686
>   NetworkManager-openvpn-0.8.1-1.fc14.i686
>   [ryniker at mini ~]$ 
> Should I see something more here?  True, as the chkconfig output
> indicated, this system is not set up to start NetworkManager during boot,
> but I believe the usual NetworkManager packages are present.  Have I
> misunderstod what you mean by "installed"?
> Anyway, I accept this is a confusing way to report a reasonable
> configuration, and not an outright bug.

I'm not sure, I admit I didn't actually check to see what provides those
dbus services, nor what error you get from dbus if you try to talk to a
service that's defined but whose provider isn't actually running at the
time :
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org

More information about the test mailing list