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.

Description of problem:

When using abrt-gui to report a crash, it pop up message that /var/spool/abrt/... is not writable and asks for an action. The text is eg:

Need writable directory, but '/var/spool/abrt/ccpp-2012-01-05-20:27:21-24154' is not writable. Move it to '/home/dkutalek/.abrt/spool' and operate on the moved copy?

This is confusing. Moved copy is nonsense. I thought it makes a copy and lost my dump by deleting dump in home. It performs a move actually! Although it says it doesn't have permissions!?

Version-Release number of selected component (if applicable):

abrt-2.0.4-14.el6.x86_64
abrt-gui-2.0.4-14.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1. 
2.
3.
  
Actual results:

moved copy :-)

Expected results:

Message is clear and consistent with actual action. 

Additional info:

Fixed in git:

commit 26587ba542c71364bcb76caa200b614ecfdc66d3
Author: Denys Vlasenko <dvlasenk>
Date:   Thu Jan 19 15:24:04 2012 +0100

    Make "Move and operate on the moved copy" message less confusing


                 _("Need writable directory, but '%s' is not writable."
-                " Move it to '%s' and operate on the moved copy?"),
+                " Move it to '%s' and operate on the moved data?"),
                 g_dump_dir_name, HOME
                 );

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0841.html