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

[giocarra]

no further informations

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Sep 29 11:12:10 2017
ExecutablePath: /usr/bin/gnome-keyring-daemon
InstallationDate: Installed on 2017-06-30 (90 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
ProcCmdline: /usr/bin/gnome-keyring-daemon --start --components=pkcs11
Signal: 6
SourcePackage: gnome-keyring
StacktraceTop:
 __correctly_grouped_prefixmb (begin=0x62 <error: Cannot access memory at address 0x62>, end=0x7fff290f2b30 "", thousands=0xc34de86960 "", grouping=0xfffffffe7fffffff <error: Cannot access memory at address 0xfffffffe7fffffff>) at grouping.c:82
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 warning: Couldn't find general-purpose registers in core file.
 PC register is not available
Title: gnome-keyring-daemon crashed with SIGABRT in __correctly_grouped_prefixmb()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1679903, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.