Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #998428 +++
Version-Release number of selected component:
abrt-2.1.6-3.fc20
Additional info:
reporter: libreport-2.1.6
cmdline: /usr/bin/python -u /usr/libexec/abrt-action-ureport
executable: /usr/libexec/abrt-action-ureport
kernel: 3.11.0-0.rc5.git4.2.fc20.i686+PAE
runlevel: N 5
type: Python
uid: 0
Truncated backtrace:
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:
verbose: 0
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>
ABRT_VERBOSE: '0'
__package__: None
getopt: <module 'getopt' from '/usr/lib/python2.7/getopt.pyc'>
__doc__: None
dd_opendir: <built-in function dd_opendir>
log1: <function log1 at 0xb741c764>
__builtins__: <module '__builtin__' (built-in)>
__file__: '/usr/libexec/abrt-action-ureport'
args: []
progname: 'abrt-action-ureport'
sys: <module 'sys' (built-in)>
DD_FAIL_QUIETLY_ENOENT: 1
__name__: '__main__'
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'>
opts: []
--- Additional comment from cickumqt on 20130819T09:56:27 ---
Created attachment 787972[details]
File: backtrace
--- Additional comment from cickumqt on 20130819T09:56:32 ---
Created attachment 787973[details]
File: environ
--- Additional comment from rmarko on 20130911T08:33:41 ---
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
--- Additional comment from cickumqt on 20130911T08:38:03 ---
(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.
--- Additional comment from endoflife on 20130916T16:54:47 ---
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:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
--- Additional comment from rmarko on 20131004T11:09:35 ---
Fixed upstream.
commit bf5d37aedb247d3b089606ecb361868febfe9ddb
Author: Richard Marko <rmarko>
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 <rmarko>
--- Additional comment from mmilata on 20131004T12:28:47 ---
*** Bug 979651 has been marked as a duplicate of this bug. ***
--- Additional comment from updates on 20131011T10:42:32 ---
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.
https://admin.fedoraproject.org/updates/gnome-abrt-0.3.2-1.fc20,abrt-2.1.8-1.fc20,libreport-2.1.8-1.fc20,satyr-0.10-1.fc20
--- Additional comment from updates on 20131011T16:50:00 ---
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:
https://admin.fedoraproject.org/updates/FEDORA-2013-18868/gnome-abrt-0.3.2-1.fc20,abrt-2.1.8-1.fc20,libreport-2.1.8-1.fc20,satyr-0.10-1.fc20
then log in and leave karma (feedback).
--- Additional comment from updates on 20131013T19:49:02 ---
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.