+++ This bug was initially created as a clone of Bug #895742 +++

Description of problem:
ABRT shows that it cannot write to a particular directory, even after asking for the administrative password.

Version-Release number of selected component (if applicable):
2.0.20-1.fc18 [Repeated from fc17]

How reproducible:
By use

Steps to Reproduce:
1. Open ABRT
2. Select an unreported report
3. Some of them will come up with the process window showing that it stopped with the words: "Processing interrupted: can't continue without writable directory".
  
Actual results:
Error described above.

Expected results:
No error.

Additional info:

--- Additional comment from Jiri Moskovcak on 2013-01-16 03:08:20 EST ---

Are these problematic reports from processes crashed running with root privileges?

--- Additional comment from KitchM on 2013-01-16 12:00:52 EST ---

I don't know.

I have found in using Fedora that there is no root access in the log-in menu.  It has been a source of much problem when trying to go to a root desktop and diagnose the problems the normal user sees.

--- Additional comment from Jiri Moskovcak on 2013-01-21 07:51:01 EST ---

Are these failing problems visible right after you run the abrt-gui (without root privileges)? And can you please try removing the abrt settings in ~/.config/abrt/settings and try the reporting again?

--- Additional comment from KitchM on 2013-01-21 16:53:58 EST ---

Yes, it only happens when abrt-gui notices a problem, pops up and I select to report the new issue.  It happened again today.

Tried your suggestion by renaming it ....bak, but same thing happened.

By the way, that last report was about colord.

--- Additional comment from Jakub Filak on 2013-01-22 12:00:36 EST ---

(In reply to comment #4)
> Yes, it only happens when abrt-gui notices a problem, pops up and I select
> to report the new issue.  It happened again today.
> 
> Tried your suggestion by renaming it ....bak, but same thing happened.
> 
> By the way, that last report was about colord.

We are not sure what is the root cause of this bug. But I prepared abrt/libreport update in the nightly builds repository which should fix this bug.

If you have time and you want to help us with testing, please update abrt/libreport packages from the nightly build repository and try to reproduce the unwanted behaviour.

And here is a link to page about ABRT nightly builds. http://rmarko.fedorapeople.org/

--- Additional comment from KitchM on 2013-01-22 17:00:40 EST ---

Although confusing, I created a file as described and added it to the yum.repos.d directory.  The nightly builds then appeared in Yum Extender and it updated everything regarding abrt.

I then got thru a number of reports just fine.  I ran into another problem, but will create a new incident report for it.

This one may just be solved.

Thanks.

--- Additional comment from Jakub Filak on 2013-01-23 02:42:43 EST ---

Thanks for all your help...really appreciated! 

Fixed in git

commit b68b28389466846ab64e9378ce606a088744b5d3
Author: Jakub Filak <jfilak>
Date:   Tue Jan 22 16:03:21 2013 +0100

    daemon: unify accessibility check before delete with dbus
    
    - we allow users to take ownership of dump dir but abrt-server doesn't
      allow to delete taken dump dirs, because abrt-server compares dump
      dir's UID element to caller's UID
    - solution: don't compare dump dir's UID element to caller's uid, just
      check file system rights like abrt-dbus
    - closes rhbz#895742
    
    Signed-off-by: Jakub Filak <jfilak>

--- Additional comment from Fedora Update System on 2013-02-05 08:37:20 EST ---

abrt-2.1.0-1.fc17,libreport-2.1.0-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abrt-2.1.0-1.fc17,libreport-2.1.0-2.fc17

--- Additional comment from Fedora Update System on 2013-02-05 08:41:29 EST ---

abrt-2.1.0-1.fc18,libreport-2.1.0-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abrt-2.1.0-1.fc18,libreport-2.1.0-2.fc18

--- Additional comment from Fedora Update System on 2013-02-07 21:18:59 EST ---

Package abrt-2.1.0-1.fc17, libreport-2.1.0-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.1.0-1.fc17 libreport-2.1.0-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-2065/abrt-2.1.0-1.fc17,libreport-2.1.0-2.fc17
then log in and leave karma (feedback).

--- Additional comment from KitchM on 2013-02-08 14:19:04 EST ---

Please close this as fixed.

Thanks for your help.

--- Additional comment from Naipaul Ojar on 2013-02-08 14:31:00 EST ---

Dear Support

This problem is back in Fedora 18.

Can we re-open against Fedora 18.