Bug 1091635

Summary: Deleting ABRT reports in the graphical tool causes XFWM to fail
Product: [Fedora] Fedora Reporter: Dan Book <grinnz>
Component: gnome-abrtAssignee: Jakub Filak <jfilak>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: grinnz, jberan, jfilak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5c8e27f031efc500bf3cb47e24dff3519ea729fc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-07 15:10:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: messages-afterdelete
none
File: messages-beforedelete none

Description Dan Book 2014-04-26 19:11:46 UTC 
Description of problem:
After deleting 40 of "my" bug reports, it says there are no problems but still has a bug report count of 2. After the system is rebooted, the XFCE window manager fails to load.

Version-Release number of selected component:
gnome-abrt-0.3.6

Additional info:
reporter:       libreport-2.2.1
kernel:         3.13.10-200.fc20.x86_64
type:           libreport
Comment 1 Dan Book 2014-04-26 19:11:48 UTC 
Created attachment 890100 [details]
File: messages-afterdelete
Comment 2 Dan Book 2014-04-26 19:11:50 UTC 
Created attachment 890101 [details]
File: messages-beforedelete
Comment 3 Dan Book 2014-04-26 19:37:11 UTC 
Additionally, this is a VirtualBox VM and I have a clone saved from before the bug reports were deleted.
Comment 4 Jakub Filak 2014-04-28 07:22:08 UTC 
It looks like that there are many problems in an inconsistent state on your disk. It is usually caused by an automatic disk cleaner or lack of disk space. Unfortunately, this kind of issue is unavoidable because ABRT relies on pure File System without any DBMS. Please remove the invalid problems manually to fix your issue and report the results here:

$ sudo rm -rf /var/tmp/abrt
$ rm -rf /home/grinnz/.cache/abrt/spool
Comment 5 Dan Book 2014-04-29 00:26:28 UTC 
This did remedy the issue, thank you. I do recall running out of disk space at one point (the disk for this VM is small) which is probably the cause. Perhaps ABRT should have a setting so it does not fill up the disk completely?
Comment 6 Jakub Filak 2014-05-07 15:10:15 UTC 
Actually ABRT have such a setting and it works fine unless something interrupts abrtd while cleaning the data (Shut down). In your case, it was probably combination of lack of disk space [1] and badly migrated problem data [2].

1: missing 'time' file
   - perhaps systemd-tmpfiles removed it

2: missing 'type' file
   - old problems didn't have this file
   - a rpmscriplet should create this file but it didn't (lack of disk space?)