Hi guys, This bug is still present on latest versions (seahorse 3.30). Why is assigned to chromium-browser package?
Hi guys,
This bug is still present on latest versions (seahorse 3.30).
Why is assigned to chromium-browser package?