I was wondering if this is still an issue since some user has reported upstream that the issue has disappeared with seahorse 2.30. If so, how can I reproduce it in order to fix it?
I was wondering if this is still an issue since some user has reported upstream that the issue has disappeared with seahorse 2.30.
If so, how can I reproduce it in order to fix it?