software-center crashed with SIGSEGV - just click on image to show more app detail and then click "close" button - boom - crash.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: software-center
roy@roy-laptop:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04
After doing a search for apps that work with "plant", I asked for more info about the app "cultivation". I then clicked on the icon that provides a screenshot closeup. Next, click on the "close" button and wait -- Ubuntu Software center crashes.
Instead the window showing the screenshot should close and return me to the screen showing the description of the "cultivation" application.
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 13 10:56:12 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
InterpreterPath: /usr/bin/python2.6
Package: software-center 1.1.11
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7ff657aa4463: mov 0xd0(%rdx),%rdx
PC (0x7ff657aa4463) ok
source "0xd0(%rdx)" (0x000000d0) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: software-center crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #518050, 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.