From Fedora Project Wiki

(clean up, split into steps)
(doh)
 
Line 5: Line 5:
# Edit {{filename|/etc/abrt/abrt.conf}} and find this line: <tt>MaxCrashReportsSize = 1000</tt>, this means that the quota is set to 1000 MB.
# Edit {{filename|/etc/abrt/abrt.conf}} and find this line: <tt>MaxCrashReportsSize = 1000</tt>, this means that the quota is set to 1000 MB.
# Set quota to a lower value (e.g. 1 MB: change the line to read <tt>MaxCrashReportsSize = 1</tt>)
# Set quota to a lower value (e.g. 1 MB: change the line to read <tt>MaxCrashReportsSize = 1</tt>)
# Restart the abrtd service with the command {{su -c 'systemctl restart abrtd.service'}}
# Restart the abrtd service with the command {{command|su -c 'systemctl restart abrtd.service'}}
# Run a complex GUI application such as Evolution
# Run a complex GUI application such as Evolution
# Crash the application: for Evolution, run {{command|pkill -SIGSEGV evolution}}
# Crash the application: for Evolution, run {{command|pkill -SIGSEGV evolution}}

Latest revision as of 17:12, 29 March 2011

Description

This test case tests the functionality of the ABRT "quota" option.


How to test

  1. Edit /etc/abrt/abrt.conf and find this line: MaxCrashReportsSize = 1000, this means that the quota is set to 1000 MB.
  2. Set quota to a lower value (e.g. 1 MB: change the line to read MaxCrashReportsSize = 1)
  3. Restart the abrtd service with the command su -c 'systemctl restart abrtd.service'
  4. Run a complex GUI application such as Evolution
  5. Crash the application: for Evolution, run pkill -SIGSEGV evolution
  6. Try this two or three times

Expected Results

  1. ABRT may save the first crash exceeding quota but with every other crash the older one should be gone and replaced by the new one
  2. If abrt-applet is running then it should notify user about both the crash and the exceeded quota