Bug 1776751 - Log spam because of secret handling
Summary: Log spam because of secret handling
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nextcloud-client
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Germano Massullo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-26 10:17 UTC by Vratislav Podzimek
Modified: 2020-05-26 18:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:20:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vratislav Podzimek 2019-11-26 10:17:33 UTC
Description of problem:
When the Nextcloud client is running, I can see the following log message:

> gnome-keyring-daemon[13126]: asked to register item /org/freedesktop/secrets/collection/login/64, but it's already registered

being logged every second to journal.

Version-Release number of selected component (if applicable):
nextcloud-client-2.6.1-1.fc30.x86_64

How reproducible:
100%

Steps to Reproduce:
1. run Nextcloud client on F30
2. log in to a Nextcloud server
3. run 'journalctl -f'

Actual results:
The above log message is being logged every second.

Expected results:
No log spam.

Additional info:
gnome-keyring-3.31.91-1.fc30.x86_64
libgnome-keyring-3.12.0-17.fc30.x86_64

Feel free to reassign this to gnome-keyring if you think it should be fixed on their side.

Comment 1 Sam Tygier 2019-12-07 23:00:45 UTC
Fixed upstream https://github.com/nextcloud/desktop/issues/1592

Comment 2 Vratislav Podzimek 2019-12-10 13:20:25 UTC
(In reply to Sam Tygier from comment #1)
> Fixed upstream https://github.com/nextcloud/desktop/issues/1592

Nice! Let's hope we get a new Fedora package soon. :)

Comment 3 Sam Tygier 2020-01-01 16:10:55 UTC
Fixed by the builds on bug 1782355

Comment 4 Vratislav Podzimek 2020-01-02 10:10:45 UTC
(In reply to Sam Tygier from comment #3)
> Fixed by the builds on bug 1782355

I can confirm the above build fixes this issue. Thanks! 

Unfortunately, it's not even in the 'updates-testing' repo yet so it's not easy for people to test and use.

Comment 5 Ben Cotton 2020-04-30 20:25:36 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2020-05-26 18:20:01 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.