| Summary: | Date column doesn't contain actual time stamp | ||
|---|---|---|---|
| Product: | [Applications] KSystemLog | Reporter: | Toralf Förster <toralf.foerster> |
| Component: | general | Assignee: | Nicolas Ternisien <nicolas.ternisien> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Toralf Förster
2010-05-31 13:25:45 UTC
Thank you. Nicolas 2010/5/31 Toralf Förster <toralf.foerster@gmx.de>: > https://bugs.kde.org/show_bug.cgi?id=240211 > > Summary: Date column doesn't contain actual time stamp > Product: KSystemLog > Version: unspecified > Platform: Gentoo Packages > OS/Version: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: general > AssignedTo: nicolas.ternisien@gmail.com > ReportedBy: toralf.foerster@gmx.de > > > Version: unspecified (using KDE 4.4.3) > OS: Linux > > Hello, under Gentoo I use a different time stamp format (it includes msec) in > /var/log/messages which results in a value of the "Date" column which does not > reflect the actual time stamp : > > 2010-05-26 21:23:18 2010-05-26T19:50:01.000+02:00 n22 > cron[22510]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons ) > 2010-05-26 21:23:18 2010-05-26T19:50:01.000+02:00 n22 > cron[22511]: (root) CMD (/usr/lib/sa/sa1 60 5) > 2010-05-26 21:23:18 2010-05-26T19:55:01.000+02:00 n22 > cron[22523]: (root) CMD (/usr/lib/sa/sa1 60 5) > > > Reproducible: Always > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug. > Under 4.6.1 The date column is now ok AFAICS however column "Host" and "Process" are empty. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |