Red Hat Bugzilla – Bug 1249101
Use timeout in abrt-console-notification.sh
Last modified: 2017-09-09 13:17:13 EDT
Description of problem: abrt-console-notification tries to run "abrt-cli status" on every login. If there is an ".lock" symlink in one of the problem directories (the directory is locked), abrt-cli waits until the locked directory is unlocked. This causes users must wait until the abrt-dbus kills the abrt-cli. It takes about ~50 seconds which is a lot. How reproducible: Always Steps to Reproduce: 1. Create .lock symlink in one of the problem directories "# ln -sf $PROBLEM_DIRECTORY/.lock " 2. Run "$ sh -l -i -c "echo test" " Actual results: abrt-cli status runs until the abrt-dbus's timeout is reached. Expected results: abrt-console-notification kills the abrt-cli after abrt-console-notification's timeout is reached (10 seconds) and prints a message about what happened. Additional information: This is easy fix and this commit fixes the issue on Fedora: https://github.com/abrt/abrt/commit/589bd45f887debcd74302c6881c9c6552e3563a7
Upstream commit fixes the issue: https://github.com/abrt/abrt/pull/1139/commits/83831bb2af42219682e3e1d4adbd350e634bd07e Related upstream testcase: https://github.com/abrt/abrt/tree/rhel7/tests/runtests/console-notifications
Created attachment 1153723 [details] Patch 1/1: console-notifications: add timeout
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. https://rhn.redhat.com/errata/RHBA-2016-2307.html