| Summary: | [abrt] NetworkManager-gnome-0.8.999-2.git20110509.fc15: g_type_check_instance: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hedayat Vatankhah <hedayatv> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | dcbw, jklimes | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:0426905c6ac445c8bdc90ba7798836f03d701c42 | ||||||||
| Fixed In Version: | NetworkManager-0.8.4-2.git20110622.fc14 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-05-27 20:23:18 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Hedayat Vatankhah
2011-05-15 13:26:15 UTC
Created attachment 499010 [details]
File: maps
Created attachment 499011 [details]
File: backtrace
The error occurred after editing (saving a connection). It would help if you are able to reproduce. Do you see any errors in .xsession-errors file in your home directory? E.g.: ... invalid connection after update: bug in the ... Well, I can both reproduce the error and see the errors in .xsession-errors. First, the errors: ** (nm-connection-editor:14233): WARNING **: edit_done_cb: invalid connection after update: bug in the 'NMSettingIP4Config' / 'routes' invalid: 1 And for reproducing the error: I had a connection which receives its config through DHCP, but I wanted to set the default gateway manually. I didn't (and still have not) figured out how to set a default gateway, so I tried different approaches. One of them was trying to add a new route by using "0.0.0.0" as its IP address, 0 as netmask, 192.168.1.2 as the gateway and 0 for metric. I also checked "Ignore automatically acquired routes". After saving the connection, the crash occurs. Thank you for your notice. Thanks for the steps for reproducing! It was very helpful. The crash is fixed upstream: 27c4558761e59716959f6ceb91491d0230ace729 (master) In addition, editor will not allow inserting 0.0.0.0 as Address and Netmask for Routes, because the default gateway is handled another way at present (taken from addresses, either manual or DHCP-provided). bdc58dd6f4ef9004dd3f8937d55a35794b7d7c76 (master) (editor: don't allow inserting 0.0.0.0 as destination and netmask for IPv4 routes) In your case, I recommend changing the default gateway in DHCP server or use manual IP configuration (and set the gateway in Gateway field in manual Addresses). If you want/need to use DHCP and still change the default gateway, I think you have to use an dispatcher script to do that: --- cut --- #!/bin/bash interface=$1 action=$2 if [ "$interface" = "eth0" -a "$action" = "up" ]; then /sbin/ip route change default via <your_default_gw_IP> dev $interface fi --- cut --- Put this to /etc/NetworkManager/dispatcher.d/01-change-default-gw This will be run whenever the interface eth0 was activated and change the default route. See man NetworkManager for more info about dispatcher scripts. Note: There is a bug in NetworkManager-0.8.999-1 and NetworkManager-0.8.999-2 dispatcher - the interface (first parameter) is empty. So you need to downgrade to NetworkManager-0.8.998-4.git20110427.fc15 or wait for next release (the fix is already upstream). Thanks for fixing the bug. However, using the dispatcher is still not an option, since I don't want to do it for all connections of an interface. I just wanted this for a single wireless connection. So, it is not possible right now. Thanks for letting me know about this. I think it would be nice to be added as a feature, specially as NetworkManager has an "ignore obtained routes" option. Thanks. :) You *can* use the dispatcher script, because the dispatcher also exports CONNECTION_ID and CONNECTION_UUID environment variables with name and UUID of the connection, respectively. So just add that to the 'if' condition. I hope we will have a better handling in future :) Some enhancements about multiple gateways are being discussed on NM mailing list. Aha, thanks! :) NetworkManager-0.8.999-3.git20110526.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/NetworkManager-0.8.999-3.git20110526.fc15 Package NetworkManager-0.8.999-3.git20110526.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.8.999-3.git20110526.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/NetworkManager-0.8.999-3.git20110526.fc15 then log in and leave karma (feedback). NetworkManager-0.8.999-3.git20110526.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. NetworkManager-0.8.4-2.git20110622.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/NetworkManager-0.8.4-2.git20110622.fc14 NetworkManager-0.8.4-2.git20110622.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. NetworkManager-0.8.4-2.git20110622.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |