window-stack-bridge crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()

[Alex Bufniță]

How it happened:
I am using DoubleCommander (doublecmd).
I have a doublecmd app shortcut locked to the unity launcher.
Up until the 13.04 release whenever I minimised DoubleCommander the launcher icon behaved as if the app was closed and it refuzed to start when I clicked on the launcher icon. The program process was still runnning.

For 13.10:
1. I minimised the app (pressed the window minimise button)
2. (The launcher showed the icon as if the app was closed although the process was still running in the background)
3. When I clicked the launcher icon again the OS Error window showed up and it led to this bug report
4. I clicked the launcher icon yet again
5. The app showed up and a duplicate app icon appeared in the launcher
6. I pressed the window close button and the app and the process were closed
7. If I press the the launcher icon again - repeat from step 5
8. If I minimise after step 5 the app does not show up - I am not able to start it again until I end the process from the System Monitor

I can't figure if it's an app problem or an OS problem.

I will try to reproduce the OS error window after I restart.

I hope this info helps.

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
Date: Mon Oct 21 01:04:09 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
InstallationDate: Installed on 2012-04-27 (541 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1a0ccc4bd4 <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+20>: mov 0x8(%rsi),%rbp
 PC (0x7f1a0ccc4bd4) 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: Upgraded to saucy on 2013-10-20 (0 days ago)
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 #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.