Description of problem: Crash occured when I was changing password to my Login keyring. It appeared right after I confirmed the new password. I run it again but this time I click on cancel in the dialog for entering new password, and it crashed again. So this crash occurs when the dialog is closed. Version-Release number of selected component: seahorse-3.30-1.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/seahorse --gapplication-service crash_function: g_variant_unref executable: /usr/bin/seahorse journald_cursor: s=ca2272b255144f8e997e635f948b899f;i=3e3b;b=9f230bd454e04ae29746af920baa8bb7;m=1149c53078;t=5774db3f4b4fb;x=f2eb86fdafafb7a1 kernel: 4.18.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_variant_unref at gvariant-core.c:625 #1 ___lambda21_ at gkr/gkr #2 ____lambda21__gasync_ready_callback at gkr/gkr #3 g_simple_async_result_complete at gsimpleasyncresult.c:802 #4 on_real_prompt_completed at libsecret/secret-service.c:322 #5 g_simple_async_result_complete at gsimpleasyncresult.c:802 #6 perform_prompt_complete at libsecret/secret-prompt.c:288 #7 on_prompt_completed at libsecret/secret-prompt.c:314 #8 emit_signal_instance_in_idle_cb at gdbusconnection.c:3711 #13 g_main_context_iteration at gmain.c:3981
Created attachment 1489802 [details] File: backtrace
Created attachment 1489803 [details] File: cgroup
Created attachment 1489804 [details] File: core_backtrace
Created attachment 1489805 [details] File: cpuinfo
Created attachment 1489806 [details] File: dso_list
Created attachment 1489807 [details] File: environ
Created attachment 1489808 [details] File: exploitable
Created attachment 1489809 [details] File: limits
Created attachment 1489810 [details] File: maps
Created attachment 1489811 [details] File: mountinfo
Created attachment 1489812 [details] File: open_fds
Created attachment 1489813 [details] File: proc_pid_status
Created attachment 1489814 [details] File: var_log_messages
*** Bug 1655265 has been marked as a duplicate of this bug. ***
*** Bug 1656226 has been marked as a duplicate of this bug. ***
Similar problem has been detected: see: sudo journalctl -S 10:46:00 -xa > seahorse-journalctl-2019-10:46:00.txt reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: seahorse crash_function: g_variant_unref executable: /usr/bin/seahorse journald_cursor: s=5b957c1339094603836b529e5334fb88;i=284ad0;b=aaacab5b1c9f4e2e87a052a3f1e67b84;m=5722f2bd32;t=57d5ce39d5dda;x=92e9846c8cd0e442 kernel: 4.19.8-300.fc29.x86_64 package: seahorse-3.30-1.fc29 reason: seahorse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1002
*** Bug 1670323 has been marked as a duplicate of this bug. ***
*** Bug 1674213 has been marked as a duplicate of this bug. ***
*** Bug 1695891 has been marked as a duplicate of this bug. ***
*** Bug 1696574 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. Open Seahorse 2. Rightclick on passwords default 3. Select change password 4. Enter the old password 5. Enter the old password as new one 6. Seahorse crashes reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/seahorse crash_function: g_variant_unref executable: /usr/bin/seahorse journald_cursor: s=299b373299804f1e8d1271a0cc7d4637;i=57265;b=6f94f0bec2b44a6abd8739b031b6c490;m=19fbefbfa6;t=587da2639cc6c;x=7e8bb3dca4b58a08 kernel: 5.0.7-200.fc29.x86_64 package: seahorse-3.30.1.1-1.fc29 reason: seahorse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Ran seahorse. Context clip on account, entered password, changed password to blank. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: seahorse crash_function: g_variant_unref executable: /usr/bin/seahorse journald_cursor: s=2a379bc4f23b46bea4619e9e1a52be6f;i=65be4c;b=e6603432f8094672acc706f577520042;m=1bd63a79;t=58c4acb096992;x=a2793078f886782e kernel: 5.1.11-200.fc29.x86_64 package: seahorse-3.30.1.1-1.fc29 reason: seahorse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1004
*** Bug 1740865 has been marked as a duplicate of this bug. ***
*** Bug 1747897 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.