Re: ['N-M is not allowed to own the service "org.freedesktop.NetworkManager"']

2010-07-02 Thread ddreamer


>On 07/02/2010 02:21 AM, ddrea...@ms93.url.com.tw
 wrote:

>> Sorry for replying late. Somehow, I didn't receive the messages. I  found

>> messages following my original one only after I viewed the archive  by topic.

>

>Hmm, are you subscribed to this list? �I'm in the habit of using "reply

>to list", so the message was sent only to the mailing list. �(I'll want

>to reconsider this habit.)

>



I am kind of newbie to mailing list. May I ask how to "reply to list"?

Did you mean replying to "networkmanager-list@gnome.org" in e-mail client 
software?

That is what I did.



>I think Dan William's suggestion should do it for you; I've recently run

>into the same bug myself, and I've also found that forcing dbus to

>reload its config files is a workaround.

>

>

>So, in summary:

> -) Undo the edits to /etc/dbus-1/NetworkManager.conf

 > -) run sudo reload dbus

> -) run sudo start network-manager

>

>And you should be set. HTH!



After doing the above, the daemon of "NetworkManager" can be activated. That is 
the good
news.

However, the nm-applet icon just disppeared after reboot. I am sure that 
notification area is
enabled

because the three short lines just having appeared to the left to the nm-applet 
icon remained
there.

What can I do next? Or what additional information should I provide to you?




--
http://isp.url.com.tw
智邦生活館免費撥接上網  電話 40661234 / 4497890 帳號 url 密碼 url___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: ['N-M is not allowed to own the service "org.freedesktop.NetworkManager"']

2010-07-02 Thread Daniel Gnoutcheff
On 07/02/2010 02:21 AM, ddrea...@ms93.url.com.tw wrote:
> Sorry for replying late. Somehow, I didn't receive the messages. I found
> messages following my original one only after I viewed the archive by topic.

Hmm, are you subscribed to this list?  I'm in the habit of using "reply
to list", so the message was sent only to the mailing list.  (I'll want
to reconsider this habit.)


> I have replaced three "deny" by "allow", which were marked at the end of the
> line as "#deny". Supposedly, strings following "#" will be ignored as
> remark.
> 
> Here is the file content of NetworkManager.conf:


OK, so it looks the security config was installed correctly, so that's
not the issue.  I'd actually advise that you undo the changes you made,
because:

 1) The file already contains all the security exceptions that are
needed, the additional exceptions you added are not necessary (and are
actually risky).

 2) While a '#' does indeed denote a "remark" in many file formats, this
does not apply to DBus config files.  These files are XML files, and XML
comments take the following form:
  
Thus, the "remarks" you added are invalid syntax, and so dbus won't load
the file.  This definitely will cause problems.

I think Dan William's suggestion should do it for you; I've recently run
into the same bug myself, and I've also found that forcing dbus to
reload its config files is a workaround.


So, in summary:
 -) Undo the edits to /etc/dbus-1/NetworkManager.conf
 -) run sudo reload dbus
 -) run sudo start network-manager

And you should be set. HTH!


Good luck,
Daniel
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: ['N-M is not allowed to own the service "org.freedesktop.NetworkManager"']

2010-07-01 Thread ddreamer



 

From: Daniel Gnoutcheff 
To: networkmanager-list gnome org
Subject: Re: ['N-M is not allowed to own the service    
"org.freedesktop.NetworkManager"']
Date: Wed, 16 Jun 2010 13:56:06 -0400

  
 
>On 06/16/2010 01:01 PM, ddreamer ms93 url com tw wrote:

>> Hi, Dear:

>> 

>> I am using Ubuntu 10.04 with regular update. There is a red exclamation

>> mark at the right lower corner of the nm-applet icon. Of course, there

>> was no signal level. Clicking it results in the message of

>> "NetworkManager is not running".

>> 

>> Looking up daemon.log, I found the following message:

>> NetworkManager:   nm_dbus_manager_start_service(): Could not

>> acquire the NetworkManager service.#012  Error: 'Connection ":1.216" is

>> not allowed to own the service "org.freedesktop.NetworkManager" due to

>> security policies in the configuration file'

>> NetworkManager:   main(): Failed to start the dbus service.

>

>Yep, that certainly would cause problems, and it's not altogether

>surprising that this would happen. The DBus system daemon has a very

>strong security policy, and daemons like NetworkManager need to setup

>specific security exceptions in order to work. Normally, this is

>something that distributions take care of, but here it seems to have

>broken somehow.

>

>More specifcally, NetworkManager needs to be able to claim the bus name

>"org.freedesktop.NetworkManager" on the DBus system bus. By default, no

>application is allowed to claim any bus names, so we need to configure

>DBus to allow N-M to claim that name.

>

>On Ubuntu, the file

>  /etc/dbus-1/system.d/NetworkManager.conf

>is supposed to take care of that. What does that file contain on your

>system?



Sorry for replying late. Somehow, I didn't receive the messages. I found

messages following my original one only after I viewed the archive by topic.

I have replaced three "deny" by "allow", which were marked at the end of the

line as "#deny". Supposedly, strings following "#" will be ignored as
remark.

Here is the file content of NetworkManager.conf:



http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>





























































































#deny

#deny



#deny











512










--
http://myhome.url.com.tw
進駐智邦社區網, 敦親睦鄰變的更輕鬆有效___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: ['N-M is not allowed to own the service "org.freedesktop.NetworkManager"']

2010-06-22 Thread Dan Williams
On Wed, 2010-06-16 at 13:56 -0400, Daniel Gnoutcheff wrote:
> On 06/16/2010 01:01 PM, ddrea...@ms93.url.com.tw wrote:
> > Hi, Dear:
> > 
> > I am using Ubuntu 10.04 with regular update. There is a red exclamation
> > mark at the right lower corner of the nm-applet icon. Of course, there
> > was no signal level. Clicking it results in the message of
> > "NetworkManager is not running".
> > 
> > Looking up daemon.log, I found the following message:
> > NetworkManager:   nm_dbus_manager_start_service(): Could not
> > acquire the NetworkManager service.#012  Error: 'Connection ":1.216" is
> > not allowed to own the service "org.freedesktop.NetworkManager" due to
> > security policies in the configuration file'
> > NetworkManager:   main(): Failed to start the dbus service.
> 
> Yep, that certainly would cause problems, and it's not altogether
> surprising that this would happen. The DBus system daemon has a very
> strong security policy, and daemons like NetworkManager need to setup
> specific security exceptions in order to work. Normally, this is
> something that distributions take care of, but here it seems to have
> broken somehow.
> 
> More specifcally, NetworkManager needs to be able to claim the bus name
> "org.freedesktop.NetworkManager" on the DBus system bus. By default, no
> application is allowed to claim any bus names, so we need to configure
> DBus to allow N-M to claim that name.
> 
> On Ubuntu, the file
>   /etc/dbus-1/system.d/NetworkManager.conf
> is supposed to take care of that. What does that file contain on your
> system?
> 
> 
> > I opened a terminal and run 'sudo start network-manager', which showed
> > OK. Seconds later, running 'sudo service network-manager status' showed
> > 'network-manager stop/waiting'. Somehow, the daemon quit on it own very
> > soon.
> 
> Yep, that's not surprising. If NetworkManager is unable to obtain its
> characteristic bus name, it quits.  The only way to use NetworkManager
> is over DBus, so it really needs to have those security exceptions in
> place in order to work at all.

For a while there's been a bug in D-Bus itself (since fixed) that if you
wrote or updated a permissions file in /etc/dbus-1/system.d, the bus
would sometimes fail to completely re-read that permissions file.  If
you run into this problem, you can sometimes:

killall -HUP dbus-daemon

and then stuff will work.  If that doesn't work, then the D-Bus
permissions listed in the file may not be correct for your distro.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: ['N-M is not allowed to own the service "org.freedesktop.NetworkManager"']

2010-06-16 Thread Daniel Gnoutcheff
On 06/16/2010 01:01 PM, ddrea...@ms93.url.com.tw wrote:
> Hi, Dear:
> 
> I am using Ubuntu 10.04 with regular update. There is a red exclamation
> mark at the right lower corner of the nm-applet icon. Of course, there
> was no signal level. Clicking it results in the message of
> "NetworkManager is not running".
> 
> Looking up daemon.log, I found the following message:
> NetworkManager:   nm_dbus_manager_start_service(): Could not
> acquire the NetworkManager service.#012  Error: 'Connection ":1.216" is
> not allowed to own the service "org.freedesktop.NetworkManager" due to
> security policies in the configuration file'
> NetworkManager:   main(): Failed to start the dbus service.

Yep, that certainly would cause problems, and it's not altogether
surprising that this would happen. The DBus system daemon has a very
strong security policy, and daemons like NetworkManager need to setup
specific security exceptions in order to work. Normally, this is
something that distributions take care of, but here it seems to have
broken somehow.

More specifcally, NetworkManager needs to be able to claim the bus name
"org.freedesktop.NetworkManager" on the DBus system bus. By default, no
application is allowed to claim any bus names, so we need to configure
DBus to allow N-M to claim that name.

On Ubuntu, the file
  /etc/dbus-1/system.d/NetworkManager.conf
is supposed to take care of that. What does that file contain on your
system?


> I opened a terminal and run 'sudo start network-manager', which showed
> OK. Seconds later, running 'sudo service network-manager status' showed
> 'network-manager stop/waiting'. Somehow, the daemon quit on it own very
> soon.

Yep, that's not surprising. If NetworkManager is unable to obtain its
characteristic bus name, it quits.  The only way to use NetworkManager
is over DBus, so it really needs to have those security exceptions in
place in order to work at all.

HTH!

Have a good one,
Daniel
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list