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 Balló György (City-busz) - Thursday, 08 June 2023, 14:33 GMT
Opened by stef204 (stef204) - Saturday, 05 March 2022, 18:47 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 14:33 GMT
|
Details
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. See: https://aur.archlinux.org/packages/gnome-keyring-git#comment-840031 And https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2a3e929650d327c5f57ec2f646b1cb749d60843 |
This task depends upon
Closed by Balló György (City-busz)
Thursday, 08 June 2023, 14:33 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#75124
Thursday, 08 June 2023, 14:33 GMT
Reason for closing: Duplicate
Additional comments about closing:
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....