gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Bug #1780627 reported by dohseven
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Expired
High
Unassigned

Bug Description

Package: gnome-keyring
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 3536
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Multi-Arch: foreign
Version: 3.28.0.2-1ubuntu1.18.04.1

------------------------------------------

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 8 15:07:49 2018
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/bin/gnome-keyring-daemon
ExecutableTimestamp: 1525893569
ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
ProcCwd: /
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 XDG_RUNTIME_DIR=<set>
Disassembly:
 => 0x7ff49ed28e97 <__GI_raise+199>: mov 0x108(%rsp),%rcx
    0x7ff49ed28e9f <__GI_raise+207>: xor %fs:0x28,%rcx
    0x7ff49ed28ea8 <__GI_raise+216>: mov %r8d,%eax
    0x7ff49ed28eab <__GI_raise+219>: jne 0x7ff49ed28ecc <__GI_raise+252>
    0x7ff49ed28ead <__GI_raise+221>: add $0x118,%rsp
    0x7ff49ed28eb4 <__GI_raise+228>: retq
    0x7ff49ed28eb5 <__GI_raise+229>: nopl (%rax)
    0x7ff49ed28eb8 <__GI_raise+232>: mov 0x3abfa9(%rip),%rdx # 0x7ff49f0d4e68
    0x7ff49ed28ebf <__GI_raise+239>: neg %eax
    0x7ff49ed28ec1 <__GI_raise+241>: mov $0xffffffff,%r8d
    0x7ff49ed28ec7 <__GI_raise+247>: mov %eax,%fs:(%rdx)
    0x7ff49ed28eca <__GI_raise+250>: jmp 0x7ff49ed28e80 <__GI_raise+176>
    0x7ff49ed28ecc <__GI_raise+252>: callq 0x7ff49ee1ec80 <__stack_chk_fail>
    0x7ff49ed28ed1: nopw %cs:0x0(%rax,%rax,1)
    0x7ff49ed28edb: nopl 0x0(%rax,%rax,1)
    0x7ff49ed28ee0 <killpg>: test %edi,%edi
SourcePackage: gnome-keyring
Stacktrace:
 #0 0x00007ff49ed28e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
         set = {__val = {512, 93934813221269, 93934813221468, 93934813221168, 93934813221468, 0, 2064, 124, 93934783944344, 140731733819248, 140688617200704, 140688613697496, 566935683072, 2048, 347476102400, 7}}
         pid = <optimized out>
         tid = <optimized out>
 #1 0x00007ff49ed2a801 in __GI_abort () at abort.c:79
         save_stage = 1
         act = {__sigaction_handler = {sa_handler = 0xfefc, sa_sigaction = 0xfefc}, sa_mask = {__val = {93934813482240, 0, 140731733819248, 140728898420737, 16564058428705303040, 72057594037927936, 16777216, 6989586621679009792, 93932964806656, 93934813482240, 0, 0, 16564058428705303040, 93934783944344, 93934813482240, 98}}, sa_flags = -1615663648, sa_restorer = 0x7ffea900bf70}
         sigs = {__val = {32, 0 <repeats 15 times>}}
 #2 0x00007ff49f88cfa5 in g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #3 0x00007ff49f88d00a in g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4 0x0000556ee564fd07 in ()
 #5 0x0000556ee564ffdd in ()
 #6 0x0000556ee5650085 in ()
 #7 0x00007ff49dd00dae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 #8 0x00007ff49dd0071f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 #9 0x00007ff49fb40761 in g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #10 0x00007ff49fb3ff6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #11 0x00007ff49fb52d3e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #12 0x00007ff49fb5a960 in g_signal_emitv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #13 0x0000556ee565f659 in ()
 #14 0x00007ff49fe5b437 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 #15 0x00007ff49fe435bc in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 #16 0x00007ff49f8660f5 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #17 0x00007ff49f8664c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #18 0x00007ff49f8667d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #19 0x0000556ee5647d7a in ()
 #20 0x00007ff49ed0bb97 in __libc_start_main (main=0x556ee5647a50, argc=3, argv=0x7ffea900cae8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffea900cad8) at ../csu/libc-start.c:310
         result = <optimized out>
         unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 1498076869208036635, 93934783333024, 140731733822176, 0, 0, 4749789229303715099, 4755462022603330843}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ff4a05fb733 <_dl_init+259>, 0x7ff4a05de6d8}, data = {prev = 0x0, cleanup = 0x0, canceltype = -1604339917}}}
         not_first_call = <optimized out>
 #21 0x0000556ee56482ca in ()
StacktraceAddressSignature: /usr/bin/gnome-keyring-daemon:6:/lib/x86_64-linux-gnu/libc-2.27.so+3ee97:/lib/x86_64-linux-gnu/libc-2.27.so+40801:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.1+72fa5:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.1+7300a:/usr/bin/gnome-keyring-daemon+2ad07:/usr/bin/gnome-keyring-daemon+2afdd:/usr/bin/gnome-keyring-daemon+2b085:/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4+5dae:/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4+571f:/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1+10761:/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1+ff6d:/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1+22d3e:/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1+2a960:/usr/bin/gnome-keyring-daemon+3a659:/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.5600.1+d7437
StacktraceTop:
 g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 ()
 ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-keyring (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
dohseven (dohseven) wrote :

You're right, sorry for the lack of context!

The issue is systematically reproduced when I boot on Ubuntu 18.04, with auto-login enabled and DESKTOP_SESSION=ubuntu. When the desktop appears, I have a window prompting my password to unlock the keyring: I enter it and then some time later (~10/15 seconds) gnome-keyring crashes.

It doesn't seem to happen if I log out of an opened session before logging back in.

Revision history for this message
dohseven (dohseven) wrote :
dohseven (dohseven)
Changed in gnome-keyring (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-keyring (Ubuntu):
status: New → Confirmed
Revision history for this message
dohseven (dohseven) wrote :

Is there anything else I can do to help tracking the bug?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Sorry it took so long to get back to that issue. Do you still use Ubuntu/see the problem?

It's a bit difficult to know what's going on from the bug informations ... if you still have the problem could add your journalctl log after getting the problem and maybe get a backtrace with libglib2.0-0-dbgsym installed (https://wiki.ubuntu.com/Debug%20Symbol%20Packages)

Changed in gnome-keyring (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-keyring (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-keyring (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.