python2.7 crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python2.7 (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
I am not entirely sure what happened. I just booted in Ubuntu and was assaulted with a bunch of appport windows. Will help debug if necessary.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: python2.7-minimal 2.7.3-15ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-9-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Mon Mar 4 21:04:05 2013
ExecutablePath: /usr/bin/python2.7
InstallationDate: Installed on 2012-11-05 (119 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: python indicator-
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb6d0b109: mov 0x4(%eax),%edx
PC (0xb6d0b109) ok
source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
?? () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: python2.7 crashed with SIGSEGV
UpgradeStatus: Upgraded to raring on 2013-02-28 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
StacktraceTop: entry=0xa448234 , link=link@ entry=0x0) at ../../dbus/ dbus-list. c:491 list_remove_ link (list=list@ entry=0xa448234 , link=0x0) at ../../dbus/ dbus-list. c:519 message_ remove_ counter (message= message@ entry=0xa4481e0 , counter=0xa3eab60) at ../../dbus/ dbus-message. c:360 connection_ message_ sent_unlocked (connection= 0xa377c48, message= message@ entry=0xa4481e0 ) at ../../dbus/ dbus-connection .c:671 <optimized out>) at ../../dbus/ dbus-transport- socket. c:680
_dbus_list_unlink (list=list@
_dbus_
_dbus_
_dbus_
do_writing (transport=