Bug 767849 - Shutdown crashes with NetworkManager error
Summary: Shutdown crashes with NetworkManager error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-15 01:05 UTC by Doug Hutcheson
Modified: 2012-08-07 16:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 16:06:27 UTC
Type: ---


Attachments (Terms of Use)

Description Doug Hutcheson 2011-12-15 01:05:50 UTC
Description of problem:
Attempting shutdown, I am seeing an error message of the following form and the shutdown hangs:
[186454.6652103]NetworkManager[930]: <error> [1323907401.574780][NetworkManagerUtils.c:519] nm_utils_call_dispatcher(): could not get dispatcher proxy!


Version-Release number of selected component (if applicable):
During update to kernel 2.6.41.1-1.fc15.x86_64 and to kernel 2.6.41.4-1.fc15.x86_64. I don't know the version number of the relevant NetworkManager.


How reproducible:
Shutdown to reboot with new kernel. I don't recall this happening when I was not updating the kernel, but I rarely shutdown unless I am updating it.


Steps to Reproduce:
1.Run PackageKit to install updates including Kernel
2.'shutdown -r now'
3.

  
Actual results:
Shutdown hangs as above


Expected results:
System should restart with the new kernel and updated kmod-nvidia


Additional info:
Looks suspiciously similar to bug https://bugzilla.redhat.com/show_bug.cgi?id=676316 for i386 FC13, FC14.

After powering down and rebooting, a grep for nm_utils in /var/log/* turns up no hits, so I cannot find any logged information.

When the shutdown is being performed to boot to a new kernel, the hang seems to occur at a time before akmod-nvidia has had a chance to finish building the new nvidia kernel module. A file of the correct name exists, but is not a valid driver and this causes the display manager to not come up upon reboot. After reboot, therefore, I go to a console and execute 'yum reinstall kmod-nvidia{version}', in the hope that a kernel module for it has been released.

Comment 1 Fedora End Of Life 2012-08-07 16:06:29 UTC
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


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