RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2068010 - Turn runtime warnings around libsecret into debug prints
Summary: Turn runtime warnings around libsecret into debug prints
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-online-accounts
Version: 8.5
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Michal Odehnal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-24 09:32 UTC by VIRENDRASINGH RAJPUT
Modified: 2023-05-16 08:41 UTC (History)
7 users (show)

Fixed In Version: gnome-online-accounts-3.28.2-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:13:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-online-accounts merge_requests 96 0 None merged goautils: Turn runtime warnings into debug prints, which they really are 2022-08-11 05:44:14 UTC
Red Hat Issue Tracker RHELPLAN-116630 0 None None None 2022-03-24 09:34:47 UTC
Red Hat Product Errata RHBA-2023:2746 0 None None None 2023-05-16 08:13:32 UTC

Description VIRENDRASINGH RAJPUT 2022-03-24 09:32:47 UTC 
Description of problem:
Customer wants to disable completely goa-daemon (gnome online accounts daemon) on the system as it spamming /var/log/messages

Mar  1 16:21:16 cesplx061 journal[111556]: secret_password_lookup_sync() returned NULL
Mar  1 16:21:16 cesplx061 journal[111556]: secret_password_lookup_sync() returned NULL
Mar  1 16:21:16 cesplx061 journal[111556]: secret_password_lookup_sync() returned NULL
Mar  1 16:21:16 cesplx061 journal[111556]: secret_password_lookup_sync() returned NULL

Customer wants to remove it from gnome because it is unnecessarily consuming cpu load and flushes logs as mentioned above.

Version-Release number of selected component (if applicable):

# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.5 (Ootpa)

# rpm -qa | grep gnome-online-accounts
gnome-online-accounts-3.28.2-3.el8.x86_64

How reproducible: Not specific steps (Not applicable)


Steps to Reproduce: Nothing specific customer just wants to completely disable goa-deamon

Actual results: We are not able to disable this goa-deamon completely from the system.


Expected results: We should able to disable this goa-deamon from the system.


Additional info:

[1] Explained customer that ideally disabling goa-daemon or removing gnome-online accounts package may make the system unstable considering it has multiple important dependencies and looking at the fact that the system is running at 'graphical.target' it is more so not recommended. 

[2] Checked internally within team found below details about goa-deamon:

 The goa-daemon program provides the org.gnome.OnlineAccounts name on the session message bus. Users or administrators should never need to start this daemon as it will be automatically started by dbus-daemon(1) whenever an application sends a D-Bus message to the org.gnome.OnlineAccounts name on the session bus.

Also, it seems to be a problem reported for Fedora :

https://bugzilla.redhat.com/show_bug.cgi?id=1379070

[3] We have tried/checked it locally as well and goa-daemon is running on the system by default. And clearly, removing the package is not an easy option. 

[4] As discussed internally with SME this is an issue also in upstream hence filling this bug to get this fixed.
Comment 1 Tomas Popela 2022-03-24 10:20:09 UTC 
We definitely won't allow the GNOME Online Software to be disabled and removed from the system as its an integral part of it (and definitely not in RHEL 8 nor in RHEL 9 due to that). We should look at fixing the warning instead, I see it has been reported in Fedora as well in https://bugzilla.redhat.com/show_bug.cgi?id=1753129 . Rishi, would you mind to take a look at this bug?
Comment 3 Debarshi Ray 2022-03-24 10:43:39 UTC 
I will dig into this in the coming weeks.  I believe that I had looked into it in the past, but ran out of time to fix it.

It's very likely a problem inside libsecret and gnome-keyring.
Comment 4 Niels De Graef 2022-05-23 15:01:16 UTC 
I investigated the fedora bz this weekend (see my last comment there) and it seems it's probably GOA having some mismatches on the strings it uses to lookup passwords in libsecret
Comment 5 Debarshi Ray 2022-06-17 19:41:41 UTC 
(In reply to Debarshi Ray from comment #3)
> I will dig into this in the coming weeks.  I believe that I had looked into
> it in the past, but ran out of time to fix it.
> 
> It's very likely a problem inside libsecret and gnome-keyring.

I finally managed to dig up my notes from the past.  It used to be quite a popular bug in the past:
https://bugzilla.gnome.org/show_bug.cgi?id=765406

However, I think that's not the same as this one.  Sorry about that.
Comment 9 Milan Crha 2022-07-22 07:51:44 UTC 
I briefly looked into the sources around that journal entry and, from my point of view, it's only a debug print on the goa side. The documentation says it's perfectly valid to have returned NULL from the secret_password_lookup_sync(), it means the required secret was not found in the keyring. That will turn the GOA account into "needs attention" state, which means the user needs to re-login to the server in the Settings->Online Accounts. I just proposed upstream [1] a change to turn the runtime warnings into the debug prints, because that's what they really are.

[1] https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/96

(In reply to Niels De Graef from comment #4)
> I investigated the fedora bz this weekend (see my last comment there) and it
> seems it's probably GOA having some mismatches on the strings it uses to
> lookup passwords in libsecret

Being this true, it's another story, but I do not see it here (it may not mean much, if I did not catch the right circumstances).

I can reproduce the runtime warning by deleting the GOA keys from the keyring (for example in seahorse). I guess it's unlikely the customer erased his/her keys, or maybe the whole keyring, after he/she configured the GOA account.

==========================================================================

Vishal, could you ask the customer to open Settings->Online Accounts and check what accounts he/she has configured there, please? If I'm not mistaken, there might be one using OAuth2, possibly a Google account. Having no accounts configured in there will stop spamming the journal, because this print is related to one of the configured accounts. Could he/she also check whether the account requires an attention? It's indicated in the Settings, the account has a warning icon on the on the right of its name and when the account is clicked, the account properties show a notice and a request to "Sign in".

If unsure, the ~/.config/goa-1.0/accounts.conf contains a list of the configured accounts. Do not share it anywhere, it's only a place to look at. The following command can show what account types are configured, without leaking any private information about the account address itself:

   $ cat ~/.config/goa-1.0/accounts.conf | grep Provider=
Comment 12 Milan Crha 2022-08-11 05:44:15 UTC 
If they do not want to use the Online Accounts then they should not define accounts there at the first place. One tricky part is Kerberos, I think GOA adds "accounts" for that on its own. What I asked for above was to verify my guesses are right. Without that they are only guesses and nothing else.

Nonetheless, the upstream approved the changes at [1]. It can be backported to RHEL.

[1] https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/96
Comment 16 errata-xmlrpc 2023-05-16 08:13:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnome-online-accounts bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2746
Note You need to log in before you can comment on or make changes to this bug.