Bug 489060
Summary: | remove useless evolution-alarm-notify-Message | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthias Clasen <mclasen> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | beland, mbarnes, mcrha |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | evolution-2.29.92 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-02-23 10:29:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthias Clasen
2009-03-07 00:22:58 UTC
In the same vain, evolution-alarm-notify has a bunch of debug spew like this: evolution-alarm-notify-Message: Setting timeout for 24653 1236402000 1236377347 evolution-alarm-notify-Message: Sat Mar 7 00:00:00 2009 That should be nuked as well, imo. Or turned from g_message into g_debug, with a log handler that suppresses LOG_LEVEL_DEBUG unless specifically triggered. Accessiblity message fixed upstream. I'll get to the other one after the code freeze. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I'm still seeing messages as reported above with evolution-2.28.2-1.fc12.i686. Here's a sample: evolution-alarm-notify-Message: Alarm callback! evolution-alarm-notify-Message: Process alarm with trigger 1266883200 evolution-alarm-notify-Message: alarm.c:249: Requested removal of nonexistent alarm! evolution-alarm-notify-Message: Setting timeout for 86400 1266969600 1266883200 evolution-alarm-notify-Message: Tue Feb 23 19:00:00 2010 evolution-alarm-notify-Message: Mon Feb 22 19:00:00 2010 The below one is correct, I turned it to a g_warning. The rest are removed upstream, will be included in 2.29.92.
> evolution-alarm-notify-Message: alarm.c:249: Requested removal of nonexistent
> alarm!
|