Description of problem:
python hook only process exception from scripts run with full path (starting with `'' character)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set ProcessUnpackaged = yes in abrt.conf and restart abrt daemon
2. echo "raise IOError" > test.py && python test.py
3. echo "raise IOError" > test.py && python $PWD/test.py
In the step 2 abrt will not catch exception
In the step 3 abrt will catch exception
Should catch exception in both cases
Looked in the source code;
if sys.argv != "/":
# Relative path - can't reliably determine package
# this script belongs to - abort dumping
# TODO: check abrt.conf and abort only if
# ProcessUnpackaged = no?
I guess it should be erased. Tried it and it works.
(In reply to comment #0)
> Description of problem:
> python hook only process exception from scripts run with full path (starting
> with `'' character)
starting with `/' character...
What would be the point in reporting a bug against a script from unknown package?
And in your example:
echo "raise IOError" > test.py && python test.py
the script isn't from any package at all. Consider the case when someone develops Python software. Do you think it would be appreciated when every crash during development will cause abrt to pop up?
My point wasn't to report a bug, but to catch an exception. I found it useful.
Anyway, if you are asking for point - what is the point of `ProcessUnpackaged' in abrt.conf?
We discussed this on mtg and decided to make it work for ProcessUnpackaged=no setting
Just to be sure - with ProcessUnpackaged=no abrt will catch exceptions for my unpackaged python script run with not absolute path?
And with ProcessUnpackaged=yes abrt will catch only exceptions for my unpackaged python script run with absolute path?
Fixed in git:
Author: Denys Vlasenko <email@example.com>
Date: Thu Oct 20 22:34:55 2011 +0200
python: allow saving of crashes in non-abspath scripts. Closes rhbz#625445.
The behavior is off by default. It can be enabled by
setting RequireAbsolutePath to "no" in /etc/abrt/plugins/python.conf.
abrt-2.0.7-2.fc16 has been submitted as an update for Fedora 16.
Package abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.7-2.fc16 libreport-2.0.8-3.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.