This bug was fixed in the package hud -
13.10.1+14.04.20131029.1-0ubuntu1

---------------
hud (13.10.1+14.04.20131029.1-0ubuntu1) trusty; urgency=low

  [ Pete Woods ]
  * Fix the ref counting of application sources The application sources
    are now entirely owned by the application-list's hash table.

  [ Ted Gould ]
  * Add apport dependencies to the package hook. (LP: #1233994)
  * Don't show disabled items in search results. (LP: #1192646)

  [ Charles Kerr ]
  * Add a nullptr safeguard to prevent a crash-on-null-ptr-reference.
    Also, move a QMap lookup outside of a for loop. Yay! . (LP:
    #1242032)
  * if we can't get the busname, log a g_critical and then exit
    gracefully instead of abort()ing in g_error. (LP: #1244688)
  * Add a null safeguard when accessing window SharedPtrs held in the
    m_windows QMap . (LP: #1243654)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 343
 -- Ubuntu daily release <ps-jenk...@lists.canonical.com>   Tue, 29 Oct 2013 
11:17:56 +0000

** Changed in: hud (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1243654

Title:
  window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId()

Status in “hud” package in Ubuntu:
  Fix Released

Bug description:
  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: Wed Oct 23 13:44:21 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2012-11-10 (346 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  SegvAnalysis:
   Segfault happened at: 0x409b70 <_ZN10BamfWindow8windowIdEv>: mov    
0x24(%rdi),%eax
   PC (0x00409b70) ok
   source "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
   BamfWindow::windowId() ()
   BamfWindowStack::ActiveWindowChanged(QString const&, QString const&) ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   OrgAyatanaBamfMatcherInterface::ActiveWindowChanged(QString const&, QString 
const&) ()
  Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId()
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  upstart.hud.log: (process:1812): hudapplicationsource-WARNING **: Unable to 
export application 'python2' skeleton on path 
'/com/canonical/hud/applications/python2': An object is already exported for 
the interface com.canonical.hud.Application at 
/com/canonical/hud/applications/python2
  upstart.window-stack-bridge.log: Could not get desktop file for 
"/org/ayatana/bamf/window/75497480"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1243654/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to     : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to