Python3 is just a symlink to python3.2 in the version this bug was
reported in, so if there is a python3 issue, it's in python3.2, not
python3-defaults. If you find this also occurs with python3.3, you can
add python3.3 to th bug by marking it as also being affected by this
issue.
** Package chan
No expert here, but I think what happened for me was.. Trying to profile
a application with out the a duma library linked. I got my error while
profiling a python script that crash with large data sets. I think other
users are not having the same problem as I am.
--
You received this bug notifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: command-not-found (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050584
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050584
Ti
Can you provide the exact command line you used to provoke this crash?
Also, though I'm not as familiar with duma as I once was with electric
fence, is it possible that duma is messing with the environment enough
to cause havoc with Python's std*?
--
You received this bug notification because you
** Visibility changed to: Public
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050584
Title:
command-not-foun
