Hi,
Every time I start firefox I'm getting the following message in the log
2015-03-26T08:43:05.397185+01:00 machine-name dbus[742]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.5658" (uid=1234 pid=27250 comm="/usr/lib64/firefox/firefox ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=782 comm="/usr/sbin/NetworkManager --no-daemon ")
Does firefox really depend on NetworkManager? I don't have NetworkManager installed, my network is started statically via /etc/rc.d/init.d/network, so the message makes kind of sense. But really, firefox depending on NetworkManager? That can't be right, can it?
Either way, is there a way to get rid of this log message other than installing NetworkManager?
Thanks, Corinna
On 03/26/2015 12:54 AM, Corinna Vinschen wrote:
Hi,
Every time I start firefox I'm getting the following message in the log
2015-03-26T08:43:05.397185+01:00 machine-name dbus[742]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.5658" (uid=1234 pid=27250 comm="/usr/lib64/firefox/firefox ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=782 comm="/usr/sbin/NetworkManager --no-daemon ")
Does firefox really depend on NetworkManager? I don't have NetworkManager installed, my network is started statically via /etc/rc.d/init.d/network, so the message makes kind of sense. But really, firefox depending on NetworkManager? That can't be right, can it?
Either way, is there a way to get rid of this log message other than installing NetworkManager?
I believe that's FireFox trying to determine if it should fire up in the "work offline" mode. I think it tries that, then tries to see if there are NICs that are up and running. If NM isn't running and if it doesn't see any NICs in the "UP, RUNNING" state, you end up in "offline" mode.
I don't know there's a way to get FF to stop logging that. It's more informational than anything else and I sure wouldn't worry about it. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If you are what you eat, then I'm fast, cheap and greasy! - ----------------------------------------------------------------------
On Thu, 2015-03-26 at 08:54 +0100, Corinna Vinschen wrote:
Either way, is there a way to get rid of this log message other than installing NetworkManager?
Yup. Navigate to about:config and create the following entry:
toolkit.networkmanager.disable: true
Works for me, somebody at Moz Corp fixed it, but they didn't make it easy to learn about that knob.
On Mar 26 14:05, John Morris wrote:
On Thu, 2015-03-26 at 08:54 +0100, Corinna Vinschen wrote:
Either way, is there a way to get rid of this log message other than installing NetworkManager?
Yup. Navigate to about:config and create the following entry:
toolkit.networkmanager.disable: true
I have this set for quite some time, but unfortunately it doesn't seem to help anymore.
Works for me, somebody at Moz Corp fixed it, but they didn't make it easy to learn about that knob.
This is with firefox 36.0.3-1 and 36.0.4-1. I have set
toolkit.networkmanager.disable: true network.manage-offline-status: false browser.offline-apps.notify: false offline.autoDetect: false services.sync.prefs.sync.browser.offline-apps.notify: false
but the log message shows up every time I start firefox. If it works for you, what is missing in my setup?!?
Thanks, Corinna
On Sat, 2015-03-28 at 10:21 +0100, Corinna Vinschen wrote: \
This is with firefox 36.0.3-1 and 36.0.4-1. I have set
toolkit.networkmanager.disable: true network.manage-offline-status: false browser.offline-apps.notify: false offline.autoDetect: false services.sync.prefs.sync.browser.offline-apps.notify: false
but the log message shows up every time I start firefox. If it works for you, what is missing in my setup?!?
Hmm. That should cover it. I was manually building up my network for months while NM had broken bridge support and I wasn't having to force Firefox online after applying that fix. I'll investigate my settings in more detail first chance I get.