Bug 1001139

Summary: Abrt uses wrong log priority for some messages.
Product: [Fedora] Fedora Reporter: Lukáš Nykrýn <lnykryn>
Component: abrtAssignee: Richard Marko <rmarko>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: abrt-devel-list, ars_1, dvlasenk, iprikryl, jberan, jfilak, jmoskovc, mmilata, mtoman, rmarko
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-abrt-0.3.3-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-01 03:53:56 UTC Type: Bug
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
journalctl output none

Description Lukáš Nykrýn 2013-08-26 14:41:44 UTC 
Description of problem:
Abrt uses wrong priority levels for some messages.

Version-Release number of selected component (if applicable):
abrt-2.1.6-3.fc19

How reproducible:
always

Steps to Reproduce:
journalctl -b -u abrtd.service -p err

Actual results:
See attached output.

Expected results:
Log messages like "Init complete, entering main loop" should not appear, when user wants to display only error and worse messages.
Comment 1 Lukáš Nykrýn 2013-08-26 14:57:07 UTC 
Created attachment 790559 [details]
journalctl output
Comment 2 Jiri Moskovcak 2013-08-27 06:28:44 UTC 
Yes, all our log messages are written to syslog as ERR:

 syslog(LOG_ERR, "%s", msg + prefix_len);

which we shouldn't.
Comment 3 Richard Marko 2013-10-27 19:29:39 UTC 
commit b50a5f7a27d5f6afe893d946b4a3278161c1fc84
Author: Richard Marko <rmarko>
Date:   Tue Oct 15 12:37:54 2013 +0200

    Use log_ family instead of VERBn log calls
    
    Related to rhbz#1001139
    
    Signed-off-by: Richard Marko <rmarko>
Comment 4 Fedora Update System 2013-10-29 04:58:10 UTC 
gnome-abrt-0.3.3-1.fc19,abrt-2.1.9-1.fc19,libreport-2.1.9-1.fc19,satyr-0.11-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gnome-abrt-0.3.3-1.fc19,abrt-2.1.9-1.fc19,libreport-2.1.9-1.fc19,satyr-0.11-1.fc19
Comment 5 Fedora Update System 2013-10-30 01:51:30 UTC 
Package gnome-abrt-0.3.3-1.fc19, abrt-2.1.9-1.fc19, libreport-2.1.9-1.fc19, satyr-0.11-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-1.fc19 abrt-2.1.9-1.fc19 libreport-2.1.9-1.fc19 satyr-0.11-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20261/gnome-abrt-0.3.3-1.fc19,abrt-2.1.9-1.fc19,libreport-2.1.9-1.fc19,satyr-0.11-1.fc19
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2013-11-01 03:53:56 UTC 
gnome-abrt-0.3.3-1.fc19, abrt-2.1.9-1.fc19, libreport-2.1.9-1.fc19, satyr-0.11-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.