kwalletd crashed with SIGSEGV in QCoreApplicationPrivate::sendPostedEvents()

[Javier Rivera]

Crashed just after login.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: kde-runtime 4:4.12.95-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Fri Mar 28 16:20:49 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/kwalletd
InstallationDate: Installed on 2013-09-27 (181 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2)
ProcCmdline: /usr/bin/kwalletd
ProcEnviron:
 LANGUAGE=gl
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=gl_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: kwalletd crashed with SIGSEGV in QCoreApplicationPrivate::sendPostedEvents()
UpgradeStatus: Upgraded to trusty on 2014-01-27 (60 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

StacktraceTop:
 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x16ee1d0) at kernel/qcoreapplication.cpp:1593
 sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
 postEventSourceDispatch (s=0x17198e0) at kernel/qeventdispatcher_glib.cpp:287
 ?? ()
 ?? ()

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!