What NetworkManager version do you run?

> Error: nmcli (0.8.997) and NetworkManager (unknown) versions don't match. Force
> execution using --nocheck, but the results are unpredictable.

You have to run nmcli that comes with NetworkManager so that they are compatible.

Hi,

> What NetworkManager version do you run?

0.8.998-2.git20110406

> 
> > Error: nmcli (0.8.997) and NetworkManager (unknown) versions don't match. Force
> > execution using --nocheck, but the results are unpredictable.
> 
> You have to run nmcli that comes with NetworkManager so that they are
> compatible.

This is exactly what I'm doing

$ rpm -qf /usr/bin/nmcli
NetworkManager-0.8.998-2.git20110406.fc15.x86_64
$ rpm -qf /usr/sbin/NetworkManager
NetworkManager-0.8.998-2.git20110406.fc15.x86_64

I noticed that this problem probably occurs only if I don't start NetworkManager during boot. Now I use normal network service and problem occurs - AFAIR when I started NetworManager during boot this problem didn't appeared. I'll try the latest NM update later.

Best regards,
Michal

(In reply to comment #2)
> Hi,
> 
> > What NetworkManager version do you run?
> 
> 0.8.998-2.git20110406

I updated to NetworkManager-0.8.998-3.git20110419.fc15.x86_64

> I noticed that this problem probably occurs only if I don't start
> NetworkManager during boot. Now I use normal network service and problem occurs
> - AFAIR when I started NetworManager during boot this problem didn't appeared.
> I'll try the latest NM update later.

Now I run only NetworkManager and I still have this problem.

Generally, there's no much use executing nmcli when NetworkManager daemon is not running, because its functionality depends on the daemon.

Some check whether NM and what version is running should be improved in nmcli, though.

(In reply to comment #4)
> Generally, there's no much use executing nmcli when NetworkManager daemon is
> not running, because its functionality depends on the daemon.

I did not say that NetworkManager daemon is not running - I just used network script during boot network configuration. Now I can use only NetworkManager, because problems with systemd service file are fixed now.

[michal@ozzy e-most]$ psc | grep NetworkManager
  546 root     cpu:/system/NetworkManager. /usr/sbin/NetworkManager --no-daemon
  995 root     cpu:/system/NetworkManager.  \_ /sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-em1.pid -lf /var/lib/dhclient/dhclient-1dad842d-1912-ef5a-a43a-bc238fb267e7-em1.lease -cf /var/run/nm-dhclient-em1.conf em1
13856 michal   name=systemd:/user/michal/2  |           \_ grep --color=auto NetworkManager
[michal@ozzy e-most]$ LANG="C" nmcli nm

** (process:13866): WARNING **: _nm_object_get_property: Error getting 'WirelessHardwareEnabled' for /org/freedesktop/NetworkManager: (9) Rejected send message, 3 matched rules; type="method_call", sender=":1.10" (uid=500 pid=13866 comm="nmcli nm ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=546 comm="/usr/sbin/NetworkManager --no-daemon "))


** (process:13866): WARNING **: _nm_object_get_property: Error getting 'WwanHardwareEnabled' for /org/freedesktop/NetworkManager: (9) Rejected send message, 3 matched rules; type="method_call", sender=":1.10" (uid=500 pid=13866 comm="nmcli nm ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=546 comm="/usr/sbin/NetworkManager --no-daemon "))


** (process:13866): WARNING **: _nm_object_get_property: Error getting 'WimaxHardwareEnabled' for /org/freedesktop/NetworkManager: (9) Rejected send message, 3 matched rules; type="method_call", sender=":1.10" (uid=500 pid=13866 comm="nmcli nm ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=546 comm="/usr/sbin/NetworkManager --no-daemon "))


** (process:13866): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager: (9) Rejected send message, 3 matched rules; type="method_call", sender=":1.10" (uid=500 pid=13866 comm="nmcli nm ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=546 comm="/usr/sbin/NetworkManager --no-daemon "))

Error: nmcli (0.8.998) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.


> 
> Some check whether NM and what version is running should be improved in nmcli,
> though.

I think I've found what's going on. NetworkManager uses "at_console" option in /etc/dbus-1/system.d/NetworkManager.conf to allow users at console make certain D-Bus calls. It contains:
<allow send_destination="org.freedesktop.NetworkManager"
       send_interface="org.freedesktop.DBus.Properties"/>

So, either you have tweaked this or you are not "at console" (most probably).
What desktop do you use? How do you login?

If you would login through gdm/kdm/xdm, etc., there is (should be)
"session    optional    pam_console.so"
in /etc/pam.d/<gdm or something> that creates /var/run/console/<user> file and everything is OK.

I reproduced the same error output by removing the /var/run/console/<user> file.

I don't have any desktop environment on this box. /var/run/console/ is empty here - so this is the case root of the problem. Whether this file should be created on system without desktop environment?

Hmm, it should work even in runlevel 3 (and works for me).
When you login, /bin/login program should use /etc/pam.d/login (where pam_console.so is configured).

'man login' for more info.

What do get on this?
rpm -q util-linux
rpm -q pam

util-linux-2.19-4.fc15.x86_64
pam-1.1.3-8.fc15.x86_64

I use a newly installed F15 (from fstab - Created by anaconda on Wed Mar 16 17:41:16 2011). I did not introduced any changes to the system except for a few custom systemd services. One thing that may be relevant - I login through ssh.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping