python3.2mu crashed with SIGABRT in Py_FatalError()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Unity |
Invalid
|
Medium
|
Unassigned | ||
| unity (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
I have no idea, about transmission?
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: python3.2-minimal 3.2.3-4
ProcVersionSign
Uname: Linux 3.5.0-13-generic i686
NonfreeKernelMo
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
Date: Sat Sep 1 23:01:50 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.2)
ProcCmdline: /usr/bin/python3.2 /usr/bin/unity-mail -c
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=tr_TR.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: python3.2
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
Py_FatalError ()
_Py_CheckRecur
PyObject_Call ()
Title: python3.2mu crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Ozgur Kucuktekin (ozgurktekin) wrote | #1 |
| Apport retracing service (apport) wrote Stacktrace.gz | #3 |
| Apport retracing service (apport) wrote StacktraceSource.txt | #4 |
| Apport retracing service (apport) wrote StacktraceTop.txt | #5 |
| Apport retracing service (apport) wrote ThreadStacktrace.gz | #6 |
| Changed in python3.2 (Ubuntu): | |
| importance: | Undecided → Medium |
| summary: |
- python3.2mu crashed with SIGABRT in raise() + python3.2mu crashed with SIGABRT in Py_FatalError() |
| tags: | removed: need-i386-retrace |
| affects: | python3.2 (Ubuntu) → unity (Ubuntu) |
| visibility: | private → public |
| Changed in unity: | |
| importance: | Undecided → Medium |
| Andrea Azzarone (azzar1) wrote | #7 |
| Changed in unity: | |
| status: | New → Invalid |
| Changed in unity (Ubuntu): | |
| status: | New → Invalid |
Does not look like it's a unity bug.