Bug 784898 - abrt won't delete last bugs
Summary: abrt won't delete last bugs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-26 15:33 UTC by Stuart D Gathman
Modified: 2012-08-13 07:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-13 07:50:22 UTC
Type: ---


Attachments (Terms of Use)
Screenshot of abrt with stubborn report highlighted (84.35 KB, image/png)
2012-01-26 15:33 UTC, Stuart D Gathman
no flags Details

Description Stuart D Gathman 2012-01-26 15:33:13 UTC
Created attachment 557689 [details]
Screenshot of abrt with stubborn report highlighted

Description of problem:
abrt refuses to delete the last (earliest) two reports in the "Not submitted control.  It did delete later reports.

Version-Release number of selected component (if applicable):
abrt-2.0.7-2.fc16.i686

How reproducible:
Not sure if it is only happening to me.

Steps to Reproduce:
1. Have lots of apps crash
2. Reports lots of bugs
3. Delete the duplicates - won't delete last 2
  
Actual results:
Delete button doesn't work on last two non submitted reports.

Expected results:
Delete button works.

Additional info:

Comment 1 Stuart D Gathman 2012-01-26 15:37:47 UTC
Just realized what is special about the 2 reports.  They were reported under a different uid. (Part of trying to isolate the bugs.)  Is there any way to delete the reports (with admin password) without creating a user with that uid again, just to delete the reports, and then deleting the user?

Comment 2 Stuart D Gathman 2012-01-26 15:38:52 UTC
The GUI should really tell you *why* it won't delete the report, instead of just doing nothing.  Something like 'that report belongs to uid xxx'.

Comment 3 Nikola Pajkovsky 2012-05-15 10:15:19 UTC
It should be with last update. There is check-box called 'Show all problems'. It will ask you for root password and than you should be able delete any problems.

Is this bug still valid to you?

Comment 4 Stuart D Gathman 2012-05-15 21:25:23 UTC
Picked up abrt-2.0.7-3 from updates-testing.  No change.  Installed abrt-cli, which makes showing the problem easier (notice uid has changed since crashes were collected):

$ abrt-cli list
@16
Directory:      /var/spool/abrt/ccpp-2011-12-11-13:43:21-19419
count:          1
executable:     /usr/bin/rhythmbox
package:        rhythmbox-2.90.1-17.git20110927.fc16
time:           Sun 11 Dec 2011 01:43:21 PM EST
uid:            902

@17
Directory:      /var/spool/abrt/ccpp-2011-12-06-18:28:59-1994
count:          1
executable:     /usr/bin/stellarium
package:        stellarium-0.11.1-1.fc16
time:           Tue 06 Dec 2011 06:28:59 PM EST
uid:            902

$ id
uid=1000(stuart) gid=902(stuart) groups=902(stuart),10(wheel),18(dialout),500(davfs2),990(wireshark) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
$ abrt-cli rm @16
'@16' does not exist
$ sudo abrt-cli rm @16
[sudo] password for stuart: 
'@16' does not exist

Comment 5 Stuart D Gathman 2012-05-15 21:28:07 UTC
I think I can just go in and rm -rf the directory reported in abrt-cli list.  But I'll keep them around in case you want me to test something.

Comment 6 Nikola Pajkovsky 2012-05-16 11:46:34 UTC
abrt-cli rm @N where N is number doesn't work. use

$ abrt-cli rm /var/spool/abrt/ccpp-2011-12-11-13:43:21-19419

Comment 7 Stuart D Gathman 2012-05-16 18:08:42 UTC
That's better, now it behaves the same as the GUI (rm silently ignored):

$ abrt-cli rm /var/spool/abrt/ccpp-2011-12-06-18:28:59-1994
$ abrt-cli list
@16
Directory:      /var/spool/abrt/ccpp-2011-12-11-13:43:21-19419
count:          1
executable:     /usr/bin/rhythmbox
package:        rhythmbox-2.90.1-17.git20110927.fc16
time:           Sun 11 Dec 2011 01:43:21 PM EST
uid:            902

@17
Directory:      /var/spool/abrt/ccpp-2011-12-06-18:28:59-1994
count:          1
executable:     /usr/bin/stellarium
package:        stellarium-0.11.1-1.fc16
time:           Tue 06 Dec 2011 06:28:59 PM EST
uid:            902

Comment 8 Stuart D Gathman 2012-05-16 18:11:57 UTC
However, doing so as root does work:

$ sudo abrt-cli rm /var/spool/abrt/ccpp-2011-12-06-18:28:59-1994
[sudo] password for stuart: 
rm '/var/spool/abrt/ccpp-2011-12-06-18:28:59-1994'
$ abrt-cli list
@16
Directory:      /var/spool/abrt/ccpp-2011-12-11-13:43:21-19419
count:          1
executable:     /usr/bin/rhythmbox
package:        rhythmbox-2.90.1-17.git20110927.fc16
time:           Sun 11 Dec 2011 01:43:21 PM EST
uid:            902

Comment 9 Jiri Moskovcak 2012-08-10 07:44:39 UTC
Can you please send us the output of:

$ ls -lZ /var/spool/abrt

and is abrtd running when you're trying to remove the bug?

Comment 10 Stuart D Gathman 2012-08-12 01:20:16 UTC
I've moved on to F17, and I've already removed the foreign reports.  Abrt on F17 now has an option to show/not show foreign (other user id) reports.

I do have the f16 root fs mounted readonly:

$ ls -lZ /f16/var/spool/abrt
-rw-r--r--. root root system_u:object_r:abrt_var_cache_t:s0 abrt-db
drwxr-x---. abrt bms  system_u:object_r:abrt_var_cache_t:s0 ccpp-2012-07-22-17:46:21-1684
-rw-------. root root system_u:object_r:abrt_var_cache_t:s0 last-ccpp

Assuming the extended attributes are consistent between the versions, the above should be informative.  They certainly look reasonable.

For contrast, here it is in F17:

$ ls -lZ /var/spool/abrt
-rw-------. root root   system_u:object_r:abrt_var_cache_t:s0 abrt-gui-coredump
drwxr-x---. abrt stuart system_u:object_r:abrt_var_cache_t:s0 ccpp-2012-07-23-19:52:01-2008
drwxr-x---. abrt stuart system_u:object_r:abrt_var_cache_t:s0 ccpp-2012-07-24-15:53:38-5890
drwxr-x---. abrt stuart system_u:object_r:abrt_var_cache_t:s0 ccpp-2012-08-01-11:23:01-1474
-rw-------. root root   system_u:object_r:abrt_var_cache_t:s0 last-ccpp
drwxr-x---. abrt root   system_u:object_r:abrt_var_cache_t:s0 pyhook-2012-08-02-14:52:11-1660

Comment 11 Jiri Moskovcak 2012-08-13 07:50:22 UTC
Thank fot the info. Closing this as it seems to be fixed. Please reopen the bug if you experience the problem again.


Note You need to log in before you can comment on or make changes to this bug.