Bug 845829
| Summary: | [abrt] NetworkManager-0.9.4.0-9.git20120521.fc17: modem_enabled_cb: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sergio Basto <sergio> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 17 | CC: | danw, dcbw, jklimes | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:82e9e49f22bdd4faf008565c21c7ad843615e513 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-01-09 19:16:52 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Sergio Basto
2012-08-05 13:10:16 UTC
Created attachment 602355 [details]
File: backtrace
Created attachment 602356 [details]
File: maps
It crashed in src/nm-device-modem.c:modem_enabled_cb() failing to get private structure NMDeviceModemPrivate. Are you still able to reproduce this. (with current software versions)? (In reply to comment #3) > It crashed in src/nm-device-modem.c:modem_enabled_cb() failing to get > private structure NMDeviceModemPrivate. > > Are you still able to reproduce this. (with current software versions)? No , I can't reproduce , also I don't remember why I send this bug report ... maybe this happened after resume after suspend , don't remember . Hi, I think this happened many times, so I send the bug report but the error disappear after sometime. So I'm going close this bug as fixed in Current release, OK ? . Thanks, |