FS#59519 - [seahorse] Filter functionality not working

Attached to Project: Arch Linux
Opened by Filipe Verri (verri) - Friday, 03 August 2018, 14:28 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 02 September 2018, 06:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Entering any string to the filter box does not update the list of passwords, certificates, etc. Pressing enter after typing the string doesn't work either. The list remains unchanged.

Additional info:
* seahorse: 3.20.0+288+gce2340dc-1
* gtk3: 3.22.30-1

Using i3 as WM.

Steps to reproduce:
1. Open seahorse
2. Select a password or certificate list
3. Type something in the filter box
4. Notice that the list remains unchanged.

I have compiled seahorse from source (https://gitlab.gnome.org/GNOME/seahorse),
commit 64031db2, and the filter functionality works as expected.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 02 September 2018, 06:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  seahorse 3.29.92+6+gdd81db31-1
Comment by Christian Bundy (christianbundy) - Tuesday, 07 August 2018, 21:55 GMT
I'm having the same problem with the same version of seahorse and gtk3, although I'm using gnome-shell 3.28.3+7+g721ce5403-1 instead of i3.

I haven't compiled seahorse from source to test, but I can verify typing into the search/filter input doesn't have any effect. I've also tried hitting enter, but that doesn't do anything either.

Please let me know if there's anything I can do to help debug.
Comment by Christian Bundy (christianbundy) - Thursday, 30 August 2018, 19:37 GMT
I've looked into this further and it turns out that this is a known bug that was resolved in newer versions of Seahorse. I've flagged the package as out-of-date with the following message:

> This package is using an arbitrary commit[0] rather than a released version, which means that we get the negatives of a non-stable release (e.g. the filter bug[1]) with no benefits. I think we should either revert back to the last stable version or stay up-to-date with new unstable versions[2], but I don't think we should remain in limbo at an arbitrary commit with open bugs.
>
> I'd be happy to volunteer my time to work on this if that's helpful. Thanks for your work maintaining this package!
>
> [0]: https://gitlab.gnome.org/GNOME/seahorse/commit/ce2340dc80820a130f9a65d0084e54443cc9c82d
> [1]: https://gitlab.gnome.org/GNOME/seahorse/issues/1#note_231075
> [2]: https://gitlab.gnome.org/GNOME/seahorse/tags

Loading...