Bug 678264

Summary: [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Scott Marshall <cyberrider>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dcbw, jklimes, timur.kristof
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:903085ded7643fb8ce83fc08529232aeb2c5ba1a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-18 08:37:05 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 Flags
File: backtrace none

Description Scott Marshall 2011-02-17 10:51:03 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nm-applet --sm-disable
component: NetworkManager
executable: /usr/bin/nm-applet
kernel: 2.6.35.11-83.fc14.x86_64
package: NetworkManager-gnome-1:0.8.1-10.git20100831.fc14
reason: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297938434
uid: 500

How to reproduce
-----
1. .
2.
3.
Comment 1 Scott Marshall 2011-02-17 10:51:06 UTC 
Created attachment 479301 [details]
File: backtrace
Comment 2 Timur Kristóf 2011-02-17 22:31:02 UTC 
Package: NetworkManager-gnome-1:0.8.1-10.git20100831.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Left click on Network Manager applet
2. Click on "Create new wireless network"
3. To the name, enter "MyAdHoc"
4. Choose "WPA/WPA2" as the security option and click on "Create"
5. On the dialog that pops up, click "Connect"


Comment
-----
Second time I tried to create the ad-hoc wifi with the saved settings of this network, it succeeded.
Comment 3 Jirka Klimes 2011-02-18 08:37:05 UTC 

*** This bug has been marked as a duplicate of bug 657352 ***