gnome-keyring-daemon: Full load

[El jinete sin cabeza]

https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25

---

Description of Problem:
After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance.

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

How reproducible:
Always.

Steps to reproducible:
1. Login with my user account and password in GDM3
2. Then I check with the 'top' program in terminal
3. I have had loads of ~ 7...11 (load average)

Actual results:
The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly

Expected results:
That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-keyring 3.28.2-3ubuntu1
Uname: Linux 5.0.0-050000rc7-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 18 12:45:51 2019
InstallationDate: Installed on 2018-12-02 (77 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Sebastien Bacher (seb128)]

Could you also add the journalctl log from around the time of the issue?

[El jinete sin cabeza (ejsc)]

Do you know of any guidelines for reporting a problem in an application when it stays in a loop?

[El jinete sin cabeza (ejsc)]

https://wiki.ubuntu.com/Backtrace#Already_running_programs

In point 5: I can not freeze the process with 'ctrl+c'

[Sebastien Bacher (seb128)]

your gdb prompt shows you managed to attach the process, can you try to type 't a a bt' instead if 'continue'?

[El jinete sin cabeza (ejsc)]

't a a bt' worked. Do you need any other information?

[Sebastien Bacher (seb128)]

Upstream might have an idea but there is nothing special in those backtraces, is seems to just be waiting for event, were they taken at the time of the issue when happening?

[El jinete sin cabeza (ejsc)]

Never stop the process 'gnome-keyring-daemon', I must close it with 'kill -9 <PID>'.

[El jinete sin cabeza (ejsc)]

Sebastien Bacher, could you create a [0]package with the version of [1]"gnome-keyring 3.31.90"? My intention is to confirm or inform what happens with this version of the application. Thanks!

[0] https://people.canonical.com/~seb128/lp1816458
[1] https://gitlab.gnome.org/GNOME/gnome-keyring/tags/3.31.90

[Sebastien Bacher (seb128)]

The newer version is in disco, https://launchpad.net/ubuntu/+source/gnome-keyring/3.31.90-1ubuntu1

[El jinete sin cabeza (ejsc)]

The problem still occurs in 'gnome-keyring 3.31.90-1ubuntu1'.