[Bug 1816458] Re: Full load

2019-02-21 Thread El jinete sin cabeza
The problem still occurs in 'gnome-keyring 3.31.90-1ubuntu1'.

** Attachment added: "gdb-gnome-keyring_3.31.90-1ubuntu1_v2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240611/+files/gdb-gnome-keyring_3.31.90-1ubuntu1_v2.txt

** Summary changed:

- Full load
+ gnome-keyring-daemon: Full load

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  gnome-keyring-daemon: Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-21 Thread Sebastien Bacher
The newer version is in disco, https://launchpad.net/ubuntu/+source
/gnome-keyring/3.31.90-1ubuntu1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
Never stop the process 'gnome-keyring-daemon', I must close it with
'kill -9 '.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread Sebastien Bacher
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?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
't a a bt' worked. Do you need any other information?

** Attachment added: "gdb-gnome-keyring-daemon-v4.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240218/+files/gdb-gnome-keyring-daemon-v4.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
't a a bt' worked. Do you need any other information? Please, just let
him know.

** Attachment added: "gdb-gnome-keyring-daemon-v3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240207/+files/gdb-gnome-keyring-daemon-v3.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
*daemon

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
** Attachment added: "gdb-gnome-keyring-deamon-v2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240206/+files/gdb-gnome-keyring-deamon-v2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
't a a bt' worked. Do you need any other information? Please, just let
him know.

(gdb) t a a bt

Thread 5 (Thread 0x7f3c397af700 (LWP 3618)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f3c3bf8aa3a in g_cond_wait_until (cond=cond@entry=0x5570a0d86c08, 
mutex=mutex@entry=0x5570a0d86c00, end_time=end_time@entry=1553438659) at 
../../../glib/gthread-posix.c:1460
#2  0x7f3c3bf110c1 in g_async_queue_pop_intern_unlocked 
(queue=0x5570a0d86c00, wait=wait@entry=1, end_time=1553438659) at 
../../../glib/gasyncqueue.c:422
#3  0x7f3c3bf116fd in g_async_queue_timeout_pop_unlocked (queue=, timeout=timeout@entry=50) at ../../../glib/gasyncqueue.c:574
#4  0x7f3c3bf69412 in g_thread_pool_wait_for_new_task (pool=) at ../../../glib/gthreadpool.c:263
#5  g_thread_pool_thread_proxy (data=) at 
../../../glib/gthreadpool.c:297
#6  0x7f3c3bf6890d in g_thread_proxy (data=0x7f3c2c0062d0) at 
../../../glib/gthread.c:805
#7  0x7f3c3bdb1164 in start_thread (arg=) at 
pthread_create.c:486
#8  0x7f3c3bcd9def in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f3c3a095700 (LWP 3102)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f3c3bf8a91f in g_cond_wait (cond=0x55709f80f5f0, 
mutex=0x55709f80f610) at ../../../glib/gthread-posix.c:1413
#2  0x55709f7a23a7 in ?? ()
#3  0x7f3c3bf6890d in g_thread_proxy (data=0x5570a0d201e0) at 
../../../glib/gthread.c:805
#4  0x7f3c3bdb1164 in start_thread (arg=) at 
pthread_create.c:486
#5  0x7f3c3bcd9def in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f3c3a896700 (LWP 2964)):
#0  0x7f3c3bccd6d9 in __GI___poll (fds=0x5570a0d38e40, nfds=3, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c3bf3fc76 in g_main_context_poll (priority=, 
n_fds=3, fds=0x5570a0d38e40, timeout=, context=0x5570a0d36e90) 
at ../../../glib/gmain.c:4228
#2  g_main_context_iterate (context=0x5570a0d36e90, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3922
#3  0x7f3c3bf40002 in g_main_loop_run (loop=0x5570a0d36f80) at 
../../../glib/gmain.c:4123
#4  0x7f3c3c17b9a6 in gdbus_shared_thread_func (user_data=0x5570a0d36e60) 
at ../../../gio/gdbusprivate.c:275
#5  0x7f3c3bf6890d in g_thread_proxy (data=0x5570a0d200a0) at 
../../../glib/gthread.c:805
#6  0x7f3c3bdb1164 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7f3c3bcd9def in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3c3b0b7700 (LWP 2963)):
#0  0x7f3c3bccd6d9 in __GI___poll (fds=0x5570a0d1d2a0, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c3bf3fc76 in g_main_context_poll (priority=, 
n_fds=1, fds=0x5570a0d1d2a0, timeout=, context=0x5570a0d1fd50) 
at ../../../glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x5570a0d1fd50, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3922
#3  0x7f3c3bf3fd9c in g_main_context_iteration (context=0x5570a0d1fd50, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:3988
#4  0x7f3c3bf3fde1 in glib_worker_main (data=) at 
../../../glib/gmain.c:5868
#5  0x7f3c3bf6890d in g_thread_proxy (data=0x5570a0d2) at 
../../../glib/gthread.c:805
#6  0x7f3c3bdb1164 in start_thread (arg=) at 
pthread_create.c:486
#7  0x7f3c3bcd9def in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3c3b8b5a80 (LWP 2962)):
#0  0x7f3c3bccd6d9 in __GI___poll (fds=0x5570a0d31950, nfds=5, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c3bf3fc76 in g_main_context_poll (priority=, 
n_fds=5, fds=0x5570a0d31950, timeout=, context=0x5570a0d1cad0) 
at ../../../glib/gmain.c:4228
#2  g_main_context_iterate (context=0x5570a0d1cad0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3922
#3  0x7f3c3bf40002 in g_main_loop_run (loop=0x5570a0d1cbc0) at 
../../../glib/gmain.c:4123
#4  0x55709f7230b5 in ?? ()
#5  0x7f3c3bbe309b in __libc_start_main (main=0x55709f722d90, argc=3, 
argv=0x7ffeae83b3a8, init=, fini=, 
rtld_fini=, stack_end=0x7ffeae83b398) at ../csu/libc-start.c:308
#6  0x55709f72360a in ?? ()


** Attachment added: "gdb-gnome-keyring-deamon.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240203/+files/gdb-gnome-keyring-deamon.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread El jinete sin cabeza
't a a bt' worked. Do you need any other information? Please, just let
him know.

** Attachment added: "gdb-gnome-keyring-deamon.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240204/+files/gdb-gnome-keyring-deamon.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-20 Thread Sebastien Bacher
your gdb prompt shows you managed to attach the process, can you try to
type 't a a bt' instead if 'continue'?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
https://wiki.ubuntu.com/Backtrace#Already_running_programs

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

** Attachment added: "gdb-gnome-keyring.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5239962/+files/gdb-gnome-keyring.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
  
  ---
  
- Description of problem:
+ 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-05rc7-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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
Do you know of any guidelines for reporting a problem in an application
when it stays in a loop?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
** Description changed:

  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:
- Forever.
+ 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-05rc7-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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
** Description changed:

  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:
  Forever.
  
  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 
team does not respond quickly
+ 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-05rc7-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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-19 Thread El jinete sin cabeza
** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
  
  ---
  
- I do not know what happens, but the gnome-keyring process occupies the
- entire processor for a long time.
+ Description of problem:
+ After logging into my session, the gnome-keyring-daemon process overloads the 
notebook. With this I have a drop in performance of important equipment.
+ 
+ Version-Release number of selected component (if applicable): Disco
+ 19.04.
+ 
+ How reproducible:
+ Forever.
+ 
+ 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 
team 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-05rc7-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)

** Attachment added: "journalctl_-b-1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5239830/+files/journalctl_-b-1.txt

** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
  
  ---
  
  Description of problem:
- After logging into my session, the gnome-keyring-daemon process overloads the 
notebook. With this I have a drop in performance of important equipment.
+ 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:
  Forever.
  
  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 
team 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-05rc7-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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-18 Thread Sebastien Bacher
Could you also add the journalctl log from around the time of the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816458] Re: Full load

2019-02-18 Thread Sebastien Bacher
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! 

** Changed in: gnome-keyring (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-keyring (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458

Title:
  Full load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs