Bug 810053
| Summary: | NetworkManager causes gnome-shell to crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan Kamens <jik> | ||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | awilliam, dcbw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-04-05 17:42:51 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752652 | ||||||
| Attachments: |
|
||||||
jon, can you say exactly what your config is wrt NM? Is the NM service actually enabled? Do you have any interfaces being controlled with the network service? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 809123 *** NM service disabled, no interfaces controlled with NM. Nominating this as a Beta NTH so we can discuss whether to pull it into RC4. My best guess as to the circumstance that produces this bug is running Shell with the NetworkManager service disabled, though I couldn't reproduce it that simply when I tried in a VM. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |
Created attachment 575255 [details] patch to fix uninitialized variable My gnome-shell was starting to get sluggish tonight, which in F16 was a sign that it was bloated from memory leaks and needed to be restarted, so I type Alt-F2 r RET to restart it. Unfortunately, when it restarted it crashed ("Oops! Logout" dialog). Then it crashed again, and again, and again. I even tried rebooting to see if I would be able to log in after the reboot. I analyzed the core dump and discovered that the NetworkManager being called by gnome-shell was using an uninitialized GError pointer. The attached patch fixes the bug. Given that this is a gnome-shell crash from which there is no recovery -- it'll apparently keep crashing no matter how many times you try to log in -- I think this fix probably needs to make it into F17.