Description of problem: Try to copy a wifi password from a txt file to the "Password" line in the "Wifi Security" tab of the settings window. Was able to reproduce this. Aplication crashes every time I try to copy the password there. Had to enter in manually to make it work. Version-Release number of selected component: nm-connection-editor-0.9.9.0-9.git20140123.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: nm-connection-editor --edit c9e70051-6b5f-4f38-965a-c9d672e3a360 crash_function: utils_update_password_storage executable: /usr/bin/nm-connection-editor kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 utils_update_password_storage at utils.c:449 #1 fill_connection at ws-wpa-psk.c:133 #2 validate at page-wifi-security.c:487 #3 connection_editor_validate at nm-connection-editor.c:220 #4 _g_closure_invoke_va at gclosure.c:840 #10 g_signal_emit_by_name at gsignal.c:3426 #11 end_change at gtkentry.c:2799 #12 paste_received at gtkentry.c:7071 #13 request_text_received_func at gtkclipboard.c:1043 #14 selection_received at gtkclipboard.c:942
Created attachment 887463 [details] File: backtrace
Created attachment 887464 [details] File: cgroup
Created attachment 887465 [details] File: core_backtrace
Created attachment 887466 [details] File: dso_list
Created attachment 887467 [details] File: environ
Created attachment 887468 [details] File: exploitable
Created attachment 887469 [details] File: limits
Created attachment 887470 [details] File: maps
Created attachment 887471 [details] File: open_fds
Created attachment 887472 [details] File: proc_pid_status
Created attachment 887473 [details] File: var_log_messages
First I could not reproduce because I used Ctrl-V, Shift-Ins, mouse middle button, etc. to paste the password. All of those work fine. Then I realized that you probably used right-click menu and its "Paste" item. This really provokes the crash. A fix committed upstream: fbdf902 utils: fix editor crash when context-menu's "Paste" item is used (rh #1089199) The fix will propagate to Fedora soon.
Another user experienced a similar problem: vpn configuration.......... reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nm-connection-editor --edit 15d0d539-0705-41ee-8547-388bd754ae24 crash_function: utils_update_password_storage executable: /usr/bin/nm-connection-editor kernel: 3.15.7-200.fc20.x86_64 package: nm-connection-editor-0.9.9.0-10.git20140123.fc20 reason: nm-connection-editor killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.