https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #7 from K.J. Petrie ---
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #6 from Nate Graham ---
No, it just means that the issue is somewhere in Qt and there's nothing we can
do about it on the KDE side. See
https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean
--
https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #5 from K.J. Petrie ---
Europe's turn last week. America's turn this week. LXQT users are also affected
so it does look like a QT problem. Does Resolved Upstream mean QT have already
found and fixed it?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #4 from Nate Graham ---
That is... extremely strange, yes. :/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #3 from K.J. Petrie ---
Thanks for looking into it. I accept it's possibly caused by an upstream
problem, but I still find it hard to understand the inconsistent treatment of
the data. Would you expect the time displayed on the clock face
https://bugs.kde.org/show_bug.cgi?id=444372
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=444372
--- Comment #1 from Nate Graham ---
*** Bug 444371 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
