Summary: | System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time" | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Garry Williams <gtwilliams> |
Component: | Assignee: | kdepim bugs <kdepim-bugs> | |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | bugs.kde.org, montel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Garry Williams
2016-06-28 21:17:42 UTC
Can't reproduce it. It seems to be a distro problem Seems to be fixed now also. Sorry for the noise. It's back with kontact-16.08.2-1.fc25.x86_64 kontact[9252]: Cannot open "/usr/share/zoneinfo/Eastern Standard Time" $ journalctl -b|grep -c 'Eastern Standard Time' 512 $ I can confirm this issue. For me it's korgac[…]: Cannot open "/usr/share/zoneinfo/W. Europe Standard Time" It may be related to the fact that I am connecting to an Exchange server through davmail. Perhaps the same issue is encountered using akonadi-ews, see https://github.com/KrissN/akonadi-ews/issues/6 Does korgac also use the QTimeZone::windowsIdTo*IanaId methods? If yes, I guess a Qt bug should be filed. Then this can be closed as RESOLVED UPSTREAM. (In reply to Erik Quaeghebeur from comment #4) > It may be related to the fact that I am connecting to an Exchange server > through davmail. I removed the davmail account yesterday, but today still the error message appears. This bug went away for me. kontact-17.08.3-1.fc27.x86_64 may have fixed it. Two systems are now *not* complaining about "Cannot open". One uses gmail and the other uses davmail for Exchange. I think this bug should now be closed. (In reply to Garry Williams from comment #6) > This bug went away for me. > > kontact-17.08.3-1.fc27.x86_64 > > may have fixed it. Two systems are now *not* complaining about "Cannot > open". One uses gmail and the other uses davmail for Exchange. > > I think this bug should now be closed. I'm afraid I must disagree. I'm also on 17.08.3 and still get the message. 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! Cannot reproduce anymore. |