lxc-ls crashed with SIGABRT in raise()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I deployed a charm to my local lxc environment.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0~rc1-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 12:04:49 2013
ExecutablePath: /usr/bin/lxc-ls
InstallationDate: Installed on 2011-10-15 (521 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
SHELL=/bin/bash
TERM=unknown
LANG=en_US.UTF-8
Signal: 6
SourcePackage: lxc
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
Py_FatalError ()
?? ()
_Py_Initialize
Title: lxc-ls crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-03-16 (4 days ago)
UserGroups:
modified.
| Curtis Hovey (sinzui) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1130809, 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.