Red Hat Bugzilla – Bug 998428
[abrt] abrt-2.1.6-3.fc20: abrt-action-ureport:57:<module>:OSError: [Errno 2] No such file or directory
Last modified: 2016-01-31 21:23:00 EST
Version-Release number of selected component:
cmdline: /usr/bin/python -u /usr/libexec/abrt-action-ureport
runlevel: N 5
abrt-action-ureport:57:<module>:OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
File "/usr/libexec/abrt-action-ureport", line 57, in <module>
dirname = os.getcwd()
OSError: [Errno 2] No such file or directory
Local variables in innermost frame:
try_parse_number: <function try_parse_number at 0xb741c87c>
error_msg_and_die: <function error_msg_and_die at 0xb741c80c>
help_text: 'Usage: abrt-action-ureport [-v]'
log: <function log at 0xb740cd4c>
getopt: <module 'getopt' from '/usr/lib/python2.7/getopt.pyc'>
dd_opendir: <built-in function dd_opendir>
log1: <function log1 at 0xb741c764>
__builtins__: <module '__builtin__' (built-in)>
sys: <module 'sys' (built-in)>
set_verbosity: <function set_verbosity at 0xb740caac>
error_msg: <function error_msg at 0xb741c7d4>
_: <function <lambda> at 0xb74131b4>
spawn_and_wait: <function spawn_and_wait at 0xb741c844>
os: <module 'os' from '/usr/lib/python2.7/os.pyc'>
Created attachment 787972 [details]
Created attachment 787973 [details]
Would you please try to locate abrt messages in one of the /var/log/messages* files so we can investigate why the directory was deleted?
Output of the following command should be enough:
zgrep -C 10 '/var/tmp/abrt/ccpp-2013-08-18-19:19:23-2461' /var/log/messages* | grep abrt
(In reply to Richard Marko from comment #3)
> Would you please try to locate abrt messages in one of the
> /var/log/messages* files so we can investigate why the directory was deleted?
> Output of the following command should be enough:
> zgrep -C 10 '/var/tmp/abrt/ccpp-2013-08-18-19:19:23-2461' /var/log/messages*
> | grep abrt
Too late. I delete bugs every 15 days.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
Author: Richard Marko <email@example.com>
Date: Tue Sep 10 16:29:58 2013 +0200
a-a-ureport: handle os errors gracefully rhbz#998428 rhbz#998197
Now it won't crash when its working directory is deleted
or when it's not able to spawn a process or it tries to spawn
missing binary. It spits proper error message instead of exception.
Signed-off-by: Richard Marko <firstname.lastname@example.org>
*** Bug 979651 has been marked as a duplicate of this bug. ***
gnome-abrt-0.3.2-1.fc20,abrt-2.1.8-1.fc20,libreport-2.1.8-1.fc20,satyr-0.10-1.fc20 has been submitted as an update for Fedora 20.
Package gnome-abrt-0.3.2-1.fc20, abrt-2.1.8-1.fc20, libreport-2.1.8-1.fc20, satyr-0.10-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.2-1.fc20 abrt-2.1.8-1.fc20 libreport-2.1.8-1.fc20 satyr-0.10-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gnome-abrt-0.3.2-1.fc20, abrt-2.1.8-1.fc20, libreport-2.1.8-1.fc20, satyr-0.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.