Bug 445225 - conf file reload issues
Summary: conf file reload issues
Alias: None
Product: Fedora
Classification: Fedora
Component: dbus
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-05 15:46 UTC by Dean Mander
Modified: 2013-03-06 03:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 14:05:07 UTC

Attachments (Terms of Use)

Description Dean Mander 2008-05-05 15:46:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5

Description of problem:
although NetworkManager is started,
I get next error when starting nm-applet (see actual results).

Didn't change any /etc/dbus setting or something.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install nm-applet
2. run it

Actual Results:
$ nm-applet

** (nm-applet:3285): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service.
  Message: 'Connection ":1.41" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file'

(nm-applet:3285): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

Expected Results:

Additional info:

Comment 1 Dean Mander 2008-05-10 12:15:45 UTC
anyone looking at this?
need more info?

Comment 2 Bug Zapper 2008-05-14 10:40:11 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 3 Dean Mander 2008-06-09 09:09:33 UTC
Removed the configuration,
then it's working again...

Comment 4 Dan Williams 2008-06-09 17:15:48 UTC
This sometimes crops up when you upgrade NM and dbus doesn't notice the change
in conf files correctly.  It takes a 'killall -HUP dbus-daemon' to fix (which
causes dbus to re-read the config files) and is a dbus issue really.  Moving to

can sometimes be triggered with a 'make install' from the NM source tree too. 
Maybe a race condition in the inotify code that doesn't notice when the file is
completely written and reads it in too early, failing validation or something?

Comment 5 Dean Mander 2008-06-09 20:09:03 UTC
Well it happened when I moved from Fedora 8 to Fedora 9 Beta,
so probably due to the NM update, as you mention...

Comment 6 Bug Zapper 2009-06-10 00:37:26 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 

Comment 7 Bug Zapper 2009-07-14 14:05:07 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.