software-center crashed with signal 5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned |
Bug Description
i wanted to uninstall wireshark because it is not showing any interfaces to capture packets. i opened the s/w centre and it just crashed.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: software-center 5.6.0-0ubuntu3 [origin: LP-PPA-
ProcVersionSign
Uname: Linux 3.8.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Wed Jun 5 14:53:34 2013
Disassembly: => 0x7fa9fff9f205: Cannot access memory at address 0x7fa9fff9f205
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_IN
SHELL=/bin/bash
Signal: 5
SourcePackage: software-center
Stacktrace:
#0 0x00007fa9fff9f205 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffaf727740
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 11 (LWP 4188):
#0 0x00007faa01ccc05e in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fa989bc7d80
Title: software-center crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
The same thing happened here... I tried to open software centre and it just got crashed. It usually works ok and when I tried to open it again, it started working as normal.
I am using Ubuntu 13.04 with gnome-shell 3.8.2 with amd64 laptop. There was a problem with software center in gnome-shell 3.8.2. It was always crashing when one was trying to open it. Refer ( #1163886 software-center crashed with signal 5 with the GNOME3 PPA on 13.04 ) this bug. It was also affecting me, but with recent updates ( I don't know which were those), it started working again.
Now, I doubt about it's correction by the updates... This bug must be a duplicate of it. Thank you.