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
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 ab
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/
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:
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.
'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
'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 not
*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/+su
** 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.
'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@e
'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 notificat
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 notif
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 receive
** 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 selecte
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
** 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
** 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
** 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 over
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:/
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
20 matches
Mail list logo
