RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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