unity-2d-panel crashed with SIGSEGV in QList<AbstractX11EventFilter*>::removeAll()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity-2d
1) Description: Ubuntu natty (development branch)
Release: 11.04
2) apt-cache policy unity-2d
unity-2d:
Installed: 3.2.2-0ubuntu1
Candidate: 3.2.2-0ubuntu1
Version table:
*** 3.2.2-0ubuntu1 0
500 http://
100 /var/lib/
3) Login normally
4) After logging in using the unity-2d option at the gdm, I logged out and logged back in using the classic desktop option
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity-2d-panel 3.2.2-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
Date: Mon Feb 7 21:37:06 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: unity-2d-panel
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fac3a588450 <_ZN5QListIP22A
PC (0x7fac3a588450) ok
source "(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
QList<
Unity2dApplica
KeyboardModifi
KeyboardModifi
QObjectPrivate
Title: unity-2d-panel crashed with SIGSEGV in QList<AbstractX
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:6203): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nm-applet:6207): Gdk-CRITICAL **: IA__gdk_
(nm-applet:6207): Gtk-CRITICAL **: IA__gtk_
visibility: | private → public |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #710304, 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.