touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #38753
[Bug 1044826] Re: python3.2mu crashed with SIGABRT in Py_FatalError()
Does not look like it's a unity bug.
** Changed in: unity
Status: New => Invalid
** Changed in: unity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1044826
Title:
python3.2mu crashed with SIGABRT in Py_FatalError()
Status in Unity:
Invalid
Status in unity package in Ubuntu:
Invalid
Bug description:
I have no idea, about transmission?
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: python3.2-minimal 3.2.3-4
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
Date: Sat Sep 1 23:01:50 2012
ExecutablePath: /usr/bin/python3.2mu
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-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
Py_FatalError ()
_Py_CheckRecursiveCall ()
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1044826/+subscriptions