FS#60461 - [seahorse] hangs while opening some keys and takes ~98% CPU
Attached to Project:
Arch Linux
Opened by Stefan Jensen (sjensen) - Wednesday, 17 October 2018, 20:07 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 18:59 GMT
Opened by Stefan Jensen (sjensen) - Wednesday, 17 October 2018, 20:07 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 18:59 GMT
|
Details
Description:
seahorse hangs suddenly while (re)opening some keys and takes almost all cpu. Additional info: downgrade to seahorse 3.20.0-2 fixes this. * package version(s) seahorse 3.30+4+g50146aa9-1 * config and/or log files etc. $seahorse (seahorse:5974): Gtk-CRITICAL **: 21:40:57.869: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed [...] Lots of messages removed [...] (seahorse:5974): Gtk-CRITICAL **: 21:40:59.233: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (seahorse:5974): seahorse-WARNING **: 21:42:40.020: already tracking progress for this part of the operation (seahorse:5974): seahorse-WARNING **: 21:42:40.020: caller is trying to begin part of task that has already ended (seahorse:5974): seahorse-WARNING **: 21:42:43.123: caller is trying to end part of task that has already ended Steps to reproduce: Start seahorse an (re)open some gpg keys. Oddly enough, this does not happen, when I open my own keys. |
This task depends upon
Bad: seahorse-3.30+4+g50146aa9-1
Bad: seahorse-3.29.92+6+gdd81db31-1
Good: seahorse-3.20.0-2