https://bugs.kde.org/show_bug.cgi?id=474016
--- Comment #7 from Nate Graham <n...@kde.org> --- Your issue is different; see Bug 475255. Being marked as RESOLVED UPSTREAM doesn't mean it's actually fixed upstream; just that the bug is an upstream issue not actionable from the KDE side. See https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean -- You are receiving this mail because: You are watching all bug changes.
