unity-2d-shell crashed with SIGSEGV in QCoreApplication::notifyInternal()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1. Installed Treesheets, but had to do it twice, as the installation seemed not taking place and somehow blocked after the "payment", while the only sign of sometihing happnening was the rolling satr in the upper right corner of the ubunt software center.
2. after having installed treesheets, went for dash looking for it in the accessories filter; looked to what was available for downloading and found something called NoName. Clicked on it.
3. Saw the software center was opened through the icon with the left arrow in the laucher, but it didn't opened the window
4. Unity froze.
5. About hal minute later unity unfroze and the crash was reported.
6. selected the software center and it was opened ina a window with the mesage: Not Fond. There isn’t a software package called “facturlinex2” in your current software sources.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-22-
NonfreeKernelMo
ApportVersion: 2.0-0ubuntu5
Architecture: i386
Date: Tue Apr 10 10:20:33 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228.1)
ProcCmdline: unity-2d-shell
ProcEnviron:
PATH=(custom, no 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 QCoreApplicatio
UpgradeStatus: No upgrade log present (probably fresh install)
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 #974484, 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.