Bug 552233
Summary: | NetworkManager disabled... | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Plug Gulp <plug.gulp> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | dcbw, dwmw2, plautrba |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-18 00:10:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Plug Gulp
2010-01-04 12:46:34 UTC
The system freeze appears to be DRM/graphics related and not NetworkManager related actually. When you say "network manager is disabled", what specifically do you mean? Is the 'Networking enabled' checkbox in the nm-applet right-click menu unchecked? Or something else? If you can, can you grab the kernel log messages with a command like this typed into a terminal: dmesg > /tmp/kernel.log and then attach that file to this bug report? (In reply to comment #1) > The system freeze appears to be DRM/graphics related and not NetworkManager > related actually. > Yep, sorry for that. I stumbled across two problem at the same time, the Networkmanager issue and the drm error. Someone has already logged a bug related to drm in bugzilla. > When you say "network manager is disabled", what specifically do you mean? Is > the 'Networking enabled' checkbox in the nm-applet right-click menu unchecked? > Or something else? > The "Networking enabled" checkbox gets automatically disabled after update. And there is no notification that the checkbox has been disabled. > If you can, can you grab the kernel log messages with a command like this typed > into a terminal: > > dmesg > /tmp/kernel.log > > and then attach that file to this bug report? As the bug is already in the database, I will avoid duplicating it here. Thanks and regards, ~Ajit *** This bug has been marked as a duplicate of bug 589108 *** |