← Back to team overview

dx-packages team mailing list archive

  1. dx-packages team
  2. Mailing list archive
  3. Message #04457

[Bug 1242339] Re: window-stack-bridge crashed with SIGSEGV in data()

  Thread Previous • Date Previous • • Thread Next 
** Description changed:

+ [Impact]
+ High impoact on our users, this is one of the highest reported issues on errors.ubuntu.com: https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7
+ 
+ [Test case]
+ Use Unity, switch between applications and try to access menus via the HUD.
+ 
+ [Rgression potential]
+ This changes behavior in the window properties retrieval. Regression potential is low since this would simply return an empty set (rather than crashing) should the window not be identifyable.
+ 
+ ---
+ 
  Just working in eclipse
  
  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 i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sun Oct 20 20:11:13 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2012-05-14 (523 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
-  PATH=(custom, no user)
-  LANGUAGE=ru
-  XDG_RUNTIME_DIR=<set>
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANGUAGE=ru
+  XDG_RUNTIME_DIR=<set>
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0xb73110d7 <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+23>:	mov    0x4(%edi),%esi
-  PC (0xb73110d7) ok
-  source "0x4(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
-  destination "%esi" ok
+  Segfault happened at: 0xb73110d7 <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+23>:	mov    0x4(%edi),%esi
+  PC (0xb73110d7) ok
+  source "0x4(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
+  destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
-  QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/i386-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&) ()
-  ?? ()
+  QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/i386-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-19 (1 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo
  upstart.window-stack-bridge.log:
-  QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.14'
-  Error getting parents for "/org/ayatana/bamf/window/75613984" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75613984 объекта не найден") 
-  Error getting parents for "/org/ayatana/bamf/window/75614083" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75614083 объекта не найден")
+  QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.14'
+  Error getting parents for "/org/ayatana/bamf/window/75613984" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75613984 объекта не найден")
+  Error getting parents for "/org/ayatana/bamf/window/75614083" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75614083 объекта не найден")

-- 
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/1242339

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

Status in Unity HUD:
  Fix Committed
Status in “hud” package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  High impoact on our users, this is one of the highest reported issues on errors.ubuntu.com: https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7

  [Test case]
  Use Unity, switch between applications and try to access menus via the HUD.

  [Rgression potential]
  This changes behavior in the window properties retrieval. Regression potential is low since this would simply return an empty set (rather than crashing) should the window not be identifyable.

  ---

  Just working in eclipse

  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 i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sun Oct 20 20:11:13 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2012-05-14 (523 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=ru
   XDG_RUNTIME_DIR=<set>
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb73110d7 <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+23>:	mov    0x4(%edi),%esi
   PC (0xb73110d7) ok
   source "0x4(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hud
  StacktraceTop:
   QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/i386-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-19 (1 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo
  upstart.window-stack-bridge.log:
   QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.14'
   Error getting parents for "/org/ayatana/bamf/window/75613984" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75613984 объекта не найден")
   Error getting parents for "/org/ayatana/bamf/window/75614083" QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75614083 объекта не найден")

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1242339/+subscriptions
  Thread Previous • Date Previous • • Thread Next