Results 1 to 3 of 3

Thread: can not shutdown as network manager's problem

  1. #1
    Join Date
    Nov 2008
    Beans
    9

    can not shutdown as network manager's problem

    I just install RTAI(real time linux) on Ubuntu 8.04. After that I can not shutdown my computer and it gives me:
    "Network Manager: nm-hal-deinit():libhal shutdown failed-Did not receive a reply. Possible causes include: the remote application didn't send a reply . the message bus security policy blocked the reply. the reply timeout expired, or the network connection was broken."


    I dont know too much about network manager.
    Is there anybody having same problem or method to solve it???

    tks

  2. #2
    Join Date
    Apr 2007
    Location
    Germany
    Beans
    952
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: can not shutdown as network manager's problem

    i've been having that problem for about a year... it never bothered me tho, since most of the time it does shut down... nm has been crashing for me ever since i got 7.04 on shutdown... Usually i just have to wait.
    A fix would be nice, nonetheless...
    Calvin: I'm being educated against my will! My rights are being trampled!
    Hobbes: Is it a right to remain ignorant?
    Calvin: I don't know, but I refuse to find out!

  3. #3
    Join Date
    Nov 2007
    Beans
    18

    Re: can not shutdown as network manager's problem

    I recently reinstalled ubuntu 8.04 on my Dell Inspiron 1501 laptop (had too much network trouble with 8.10 and went back to 8.04!) and experienced the same problem (it wasn't there in a previous 8.04 install maybe a year earlier). I found a workaround for my case:

    Under: System|Administration|Services|
    Uncheck: Power management (acpid)

    Now the system shuts down completely - including power shutoff. From all the postings I read on the subject, I gather that the problem is related to a NewtworkManager bug and its relation to the ACPI power management system. The above workaround disables the startup of the ACPI daemon (I assume!) and that seems to solve the problem. I don't know what other side-effects not running acpid has. So be warned...

    Here's part of the error message I was getting before I applied the workaround:

    NetworkManager: <WARN> nm_hal_deinit(): libha1 shutdown failed - Did not receive a reply. Possible causes include:...
    Last edited by SaberCat; April 22nd, 2009 at 04:05 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •