Project

General

Profile

Bug #10209

Process gnome-keyring-daemon terminated by SIGSEGV on MATE start

Added by Michal Nowak 9 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
OI-Userland
Target version:
-
Start date:
2019-01-10
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

After update of gnome/gnome-keyring to 3.28.2-2018.0.0.0, gnome-keyring-daemon dumps core on every MATE start (although it's likely then restarted as I have it running, so no real disruption).

$ mdb core
Loading modules: [ libc.so.1 ld.so.1 ]
> ::status
debugging core file of gnome-keyring-d (64-bit) from lenovo
file: /usr/bin/gnome-keyring-daemon
initial argv: gnome-keyring-daemon --start
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), addr=4
> $C
fffffd7fffdff740 libc.so.1`mutex_destroy+0x10(0)
fffffd7fffdff760 libglib-2.0.so.0.5800.2`g_mutex_clear+0x14()
fffffd7fffdff780 gkd_ssh_agent_preload_finalize+0x71()
fffffd7fffdff7c0 libgobject-2.0.so.0.5800.2`g_object_unref+0x1c9()
fffffd7fffdff7e0 gkd_ssh_agent_service_finalize+0x38()
fffffd7fffdff820 libgobject-2.0.so.0.5800.2`g_object_unref+0x1c9()
fffffd7fffdff850 egg_cleanup_perform+0x37()
fffffd7fffdff8c0 main+0x2fb()
fffffd7fffdff8f0 _start_crt+0x83()
fffffd7fffdff900 _start+0x18()

History

#1

Updated by Hubert Garavel 7 months ago

I confirm the bug. In almost every user directory, one can find a "core" file
created by gnome-keyring-daemon.

Also, error messages are written to the boot console and to /var/adm/messages,
especially:

        gnome-keyring-daemon : could't allocate secure memory to keep passwords
#2

Updated by Michal Nowak 7 months ago

Secure memory support is not implemented on illumos, the warning might be disabled in GNOME keyring.

Also available in: Atom PDF