| Summary: | PackageKit logs at too high level | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Kyral <mkyral> | ||||
| Component: | PackageKit | Assignee: | Richard Hughes <rhughes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | jonathan, kparal, rdieter, rhughes, smparrish | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-12-05 18:47:29 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: | |||||
| Attachments: |
|
||||||
Most probably a duplicate of bug 781807. *** This bug has been marked as a duplicate of bug 781807 *** |
Created attachment 832534 [details] PackageKit logging at ERROR+ Description of problem: After update to F20 I noticed, taht PackageKit started spamming my consoles (and the notification daemon, too) with messages about all its activity (start / stop deamnon, running transactions etc.). It is VERY annoying and important stuff (such as confirmation of yum t-action) can get lost or TUI of applications like vim can be borked in the flood of the useless PackageKit messages. I suppose that it can be caused by too high log level for PackageKit (in journalctl, all the PackageKit entries are red which means ERROR or higher), but I haven't found out how to get rid of it (I know for sure I haven't fiddle with it at all). Version-Release number of selected component (if applicable): PackageKit-0.8.14-1.fc20.x86_64 How reproducible: Steps to Reproduce: 1. log in GUI and start your preferred terminal 2. 3. Actual results: consoles and notifications spammed every few minutes Expected results: silence unless actual error occurs Additional info: