window-stack-bridge crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hud (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I do not know how to reproduce this exactly.
I logged out then tried to log-in again.
The login screen was behaving as if the password was being checked and it stayed that way for a few minutes.
I logged in into tty2 and sudo shutdown now
When the system restarted and I logged in again this error showed up.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: hud 13.10.1+
ProcVersionSign
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/
ExecutableTimes
InstallationDate: Installed on 2012-04-27 (541 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcCwd: /home/alexxx
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_US
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f1a0ccc4bd4 <_ZN22QDBusAbst
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:
QDBusAbstractI
BamfWindow:
BamfWindowStac
WindowStackAda
?? ()
Title: window-stack-bridge crashed with SIGSEGV in QDBusAbstractIn
UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago)
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.