unity-2d-shell crashed with SIGSEGV in KeyMonitor::registerEvents()

Bug #965464 reported by noirtim on 2012-03-26
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d
Medium
Paweł Stołowski
unity-2d (Ubuntu)
Medium
Unassigned

Bug Description

Unity crashed during beginning of a VNC connection. Called as /etc/X11/Xsession with option XKL_XMODMAP_DISABLE=1.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 11:47:16 2012
ExecutablePath: /usr/bin/unity-2d-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: unity-2d-shell
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
Title: unity-2d-shell crashed with SIGSEGV in KeyMonitor::registerEvents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

noirtim (timfarmer) wrote :

StacktraceTop:
 KeyMonitor::registerEvents (this=0x1cd1ec0) at /build/buildd/unity-2d-5.8.0/libunity-2d-private/src/keymonitor.cpp:102
 KeyMonitor::KeyMonitor (this=0x1cd1ec0, parent=<optimized out>) at /build/buildd/unity-2d-5.8.0/libunity-2d-private/src/keymonitor.cpp:43
 KeyMonitor::instance () at /build/buildd/unity-2d-5.8.0/libunity-2d-private/src/keymonitor.cpp:56
 HotModifier::HotModifier (this=0x1bc8140, modifiers=<optimized out>, parent=<optimized out>) at /build/buildd/unity-2d-5.8.0/libunity-2d-private/src/hotmodifier.cpp:40
 KeyboardModifiersMonitor::getHotModifierFor (this=0x1ae8150, modifiers=<optimized out>) at /build/buildd/unity-2d-5.8.0/libunity-2d-private/src/keyboardmodifiersmonitor.cpp:133

Changed in unity-2d (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Gerry Boland (gerboland) on 2012-03-30
visibility: private → public
Changed in unity-2d:
importance: Undecided → Medium
assignee: nobody → Pawel Stolowski (stolowski)
Paweł Stołowski (stolowski) wrote :

Hi noirtim, could you please attach your ~/.vnc/xstartup file (I assume you modified it, and added XKL_XMODMAP_DISABLE=1 there)?

Changed in unity-2d:
status: New → Confirmed
Changed in unity-2d:
status: Confirmed → In Progress
Paweł Stołowski (stolowski) wrote :

I can reproduce the problem with the following:

1. Have the following ~/.vnc/xstartup file:

#!/bin/sh
export XKL_XMODMAP_DISABLE=1
valgrind --trace-children=yes -v unity-2d-shell &

2. Run vncserver - log file will be created in ~/.vnc. You don't have to connect with vncviewer, it will just crash after a few seconds.

Note that I had to run it via valgrind, otherwise the stacktrace I was getting was completly useless. Attaching valgrind output.
The problem appears to be in XListInputDevices returning NULL list ptr, while indicating positive number of devices.

Paweł Stołowski (stolowski) wrote :

Please note, with the proposed patch (lp:~stolowski/unity-2d/check-xlistinputdevices-ptr), we're still affected by https://bugs.launchpad.net/utouch-geis/+bug/973539 causing crash with remote sessions.

Changed in unity-2d:
status: In Progress → Fix Committed
Gerry Boland (gerboland) on 2012-04-12
Changed in unity-2d:
milestone: none → 5.10.0
Didier Roche (didrocks) on 2012-04-12
Changed in unity-2d:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-2d - 5.10.0-0ubuntu1

---------------
unity-2d (5.10.0-0ubuntu1) precise-proposed; urgency=low

  * New upstream release:
    - unity-2d-shell crashed with SIGSEGV in
      QCoreApplication::notifyInternal() (LP: #918566)
    - Unity-2d-shell crashes on startup on 64bit machines with 20+ tiles in
      launcher (LP: #967012)
    - Unity 2-d launcher doesn't hide or display properly (LP: #940590)
    - [dash] search terms aren't applied on lens change / dash show
      (LP: #947985)
    - [5.8 pre staging] "sticky edge" option does nothing visible
      (LP: #961285)
    - [dash] Maximise, then restore - much of background not removed from
      screen (LP: #968215)
    - [hud] shows up when using ctrl+alt and pressing alt first (LP: #972318)
    - [UIFe] Dash - No message displayed when no results are returned in the
      Dash (LP: #711199)
    - Missing lens shortcuts (Super-A, Super-F) (LP: #834078)
    - [dash] Unable to scroll Filter Results (LP: #920878)
    - [launcher] stays open if you mouseOut before reveal animation completes
      (LP: #943296)
    - HUD on wrong screen on mutli monitor system (LP: #947145)
    - [a11y] Orca reports "Shell" when opening HUD, Dash or Launcher
      (LP: #948033)
    - multimonitor: Please give me a way to turn off sticky monitor edges
      (LP: #946104)
    - [dash] Esc key behavior inconsistent with Unity (LP: #966121)
    - toggling the spread from the launcher does not work (LP: #968146)
    - unity-2d-shell crashed with SIGSEGV in KeyMonitor::registerEvents()
      (LP: #965464)
    - [Dash] Focus is lost when switching with the mouse (LP: #974235)
    - Multiple items selected in HUD list (LP: #948441)
    - Hud hides launcher even if set to always show (LP: #948960)
    - [launcher] Pointer reveal barrier should be 1 way only (LP: #960175)
    - [hud] connection to HUD being created on startup (LP: #965106)
    - [dash] On 1024x786 screen, dash not fullscreen so border truncated
      (LP: #967305)
  * debian/20_ubuntu-2d-gconf-default:
    - set a default key for HUD showing on Alt, in case unity-3d isn't
      installed or run before unity-2d.
  * debian/control:
    - bump libnux-2.0-dev to latest for ABI break
 -- Didier Roche <email address hidden> Thu, 12 Apr 2012 11:02:08 +0200

Changed in unity-2d (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers