Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#74037 - glib2 2.70 breaks gnome keyring

Attached to Project: Arch Linux
Opened by stef204 (stef204) - Saturday, 05 March 2022, 18:47 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 08 March 2022, 06:12 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Description: glib2 2.70 breaks gnome-keyring 1:40.0-1.

Downgrading to glib2 2.68 "fixes" issue.

OR, keeping glib2 2.70 but compiling gnome-keyring without libcap-ng "fixes" issue.


This task depends upon

Comment by Jan Alexander Steffens (heftig) - Wednesday, 06 April 2022, 21:21 GMT
What exactly breaks? It seems to work fine for me.
Comment by stef204 (stef204) - Wednesday, 20 April 2022, 21:13 GMT
It's explained in the Gentoo link above.

How it manifests itself is that the agent no longer starts gnome-keyring properly, libsecret / secret-tool, seahorse, etc., no longer work, it breaks the whole chain of apps which uses gnome-keyring....
So far, I've chosen to update glib2 to latest version BUT recompile gnome-keyring "--without-libcap-ng" and that works.
Let me know if this should be a gnome-keyring bug instead of a glib2 bug, perhaps. I am not sure which way to go here. I just need this to be addressed.

NOTE: at the time of posting the bug, I was using glib2.2.70 and gnome-keyring 1:40.0-1.
I have not recompiled since the temp fix above.

EDIT: I have now installed glib2 2.72.1-1 and am still running gnome-keyring 1:40.0-1 compiled with "--without-libcap-ng". Everything seems to work correctly (with that compilation option.)

So, I do not know if this is glib2 bug or gnome-keyring bug....
Comment by Jan Alexander Steffens (heftig) - Wednesday, 20 April 2022, 22:06 GMT
And again, I can't reproduce this problem. It works fine for me.