abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: nm-applet --sm-disable comment: gh component: NetworkManager executable: /usr/bin/nm-applet kernel: 2.6.32.11-99.fc12.i686.PAE package: NetworkManager-gnome-1:0.7.998-2.git20100106.fc12 rating: 4 reason: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. turn on the computer 2. 3.
Created attachment 407034 [details] File: backtrace
How to reproduce ----- 1. turn on the computer with wireless 2. 3. Comment ----- If a execute from the terminal as root, it doesn't happens.
upstream fix is: cd1cb9193440df97bcfc2f0c313b72eb095a59dc thanks!
*** Bug 544030 has been marked as a duplicate of this bug. ***
NetworkManager-0.8.0-8.git20100426.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-8.git20100426.fc13
NetworkManager-0.8.0-8.git20100426.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-8.git20100426.fc12
NetworkManager-0.8.0-8.git20100426.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-8.git20100426.fc13
NetworkManager-0.8.0-8.git20100426.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-8.git20100426.fc12
NetworkManager-0.8.0-9.git20100429.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-9.git20100429.fc13
NetworkManager-0.8.0-11.git20100503.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-11.git20100503.fc13
NetworkManager-0.8.0-11.git20100503.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-11.git20100503.fc12
NetworkManager-0.8.0-11.git20100503.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.8.0-12.git20100504.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-12.git20100504.fc13
NetworkManager-0.8.0-12.git20100504.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-12.git20100504.fc12
NetworkManager-0.8.0-12.git20100504.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.8.1-0.1.git20100510.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/NetworkManager-0.8.1-0.1.git20100510.fc12
NetworkManager-0.8.1-0.1.git20100510.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 600003 has been marked as a duplicate of this bug. ***