Running 13.10 and doing various tasks and it crashed and this report was generated.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: hud 13.10.1+13.10.20131014-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 25 11:39:34 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
InstallationDate: Installed on 2013-06-29 (117 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f338c2cabd4 <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+20>: mov 0x8(%rsi),%rbp
PC (0x7f338c2cabd4) ok
source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hud
StacktraceTop:
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
BamfWindow::xProp(QString const&) ()
BamfWindowStack::GetWindowProperties(unsigned int, QString const&, QStringList const&) ()
WindowStackAdaptor::GetWindowProperties(unsigned int, QString const&, QStringList const&) ()
?? ()
Title: window-stack-bridge crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1242032, 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.