Red Hat Bugzilla – Full Text Bug Listing
|Summary:||[audit-viewer] Invalid date display in 'Date Filter' tab of Audit Viewer.|
|Product:||[Fedora] Fedora||Reporter:||Lijun Li <lijli>|
|Component:||audit-viewer||Assignee:||Miloslav Trmač <mitr>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-08-01 01:04:40 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Lijun Li 2012-03-08 04:43:02 EST
Description of problem: Invalid date display in 'Date Filter' tab of Audit Viewer. Version-Release number of selected component (if applicable): audit-viewer-0.7.3-1.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install Fedora-17-Nightly-20120305.08-x86_64-Live-desktop.iso from http://alt.fedoraproject.org/pub/alt/nightly-composes/ 2. Run command audit-viewer * If not installed, As root run "yum install audit-viewer" 3. Double-click 'Filter:None' field to pops-up the 'List 1 Properties' window, and click 'Data Filter' tab, check the 'Limit to events not earlier than:' checkbox, change the date to the end of month(ex.03/31/2012) via clicking the calendar next to 'Specific time' field, and click 'OK'. 4. Double-click 'Filter:' field to pops-up the 'List 1 Properties' window again, and click 'Data Filter' tab. Actual results: The date to be changed as an invalid date(long time date: 11/26/4428732 ) after 'Specific time' in 'Data Filter' tab. Expected results: The date should be displayed as correct via changes in calendar. Additional info:
Comment 1 Lijun Li 2012-03-08 04:44:25 EST
Created attachment 568557 [details] Invalid date display in 'Date Filter' tab of Audit Viewer.
Comment 2 Lijun Li 2012-03-08 04:44:57 EST
It's reproduced on en_US.
Comment 3 Miloslav Trmač 2012-03-08 09:22:59 EST
Thanks for your report. This seems to work fine on F16, I'll need to investigate more.
Comment 4 Lijun Li 2012-03-09 01:49:02 EST
Same issue reproduced on 'Report * Properties ' window.
Comment 5 Miloslav Trmač 2012-09-21 12:00:17 EDT
Can you still reproduce this? I have tested Fedora 17 with these components > audit-viewer-0.7.3-1.fc17.x86_64 > gtk2-2.24.11-1.fc17.x86_64 > pygtk2-2.24.0-4.fc17.x86_64 in en_US, en_US.UTF-8 and cs_CZ.UTF-8, and everything seems to work fine. Unfortunately the original live image is no longer available, so I can't check that for comparison.
Comment 6 Miloslav Trmač 2012-09-21 14:30:35 EDT
I strongly suspect this is caused by bug #859524, but having a reproducer would allow us to make sure.
Comment 7 Fedora End Of Life 2013-07-03 21:00:07 EDT
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 8 Fedora End Of Life 2013-08-01 01:04:43 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.