signon-ui crashed with SIGABRT in __libc_message()

[userDepth]

Don't know where this crash came form.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: signon-ui 0.11-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Sat Sep 29 18:41:27 2012
ExecutablePath: /usr/bin/signon-ui
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: /usr/bin/signon-ui
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: signon-ui
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 QString::free(QString::Data*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: signon-ui crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #1040580. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f816d08cfd0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f816d089f99 "invalid fastbin entry (free)", ptr=<optimized out>) at malloc.c:5007
 QString::free(QString::Data*) () from /tmp/tmpVIcg71/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /tmp/tmpVIcg71/usr/lib/x86_64-linux-gnu/libQtDBus.so.4
 QDBusMessage::~QDBusMessage() () from /tmp/tmpVIcg71/usr/lib/x86_64-linux-gnu/libQtDBus.so.4

[Launchpad Janitor (janitor)]

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

[Jake McGregor (jake-mcgregor86)]

This pops up for me every once in a while. I think this might affect 14.10 alpha as well, but it could be the affected component is still from 14.04 and hasn't been changed for 14.10.

[Jake McGregor (jake-mcgregor86)]

I forgot to add, it might be relevent that I have Spanish set as my default language. I didn't think it would matter but I wasn't sure.