[opensuse-kde] Upstream Kmail 2 Bug open since 23-01-2017 - still present in 5.10.3
Dear openSUSE KDE team, Is there anyone that can have a look and possibly escalate upstream bug ID 375445? https://bugs.kde.org/show_bug.cgi?id=375445 It has been open since 23/01/17 (first reported in Kmail2 5.7.0) with apparently zero developer activity on it since it was reported. Thanks in anticipation. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
In data lunedì 22 aprile 2019 15:37:21 CEST, Rodney Baker ha scritto:
It has been open since 23/01/17 (first reported in Kmail2 5.7.0) with apparently zero developer activity on it since it was reported.
While I don't know about the CPU usage (I can't reproduce it), I can tell you that unfortunately the mails not being displayed (if inline) is a limitation of the Qt engine used to display them (QWebEngine) which tops at a rather low value (I can't check which one, but it was a handful of Mb). This issue ineeds to be handled in Qt, if fixable. As an aside, you can't really "escalate" bugs. Best is to triage them to help developers find them: there are few PIM developers overall and the number of bugs in bugs.kde.org pretty large (including also duplicate, invalid, support requests mis-filed as bugs...). -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
On Tuesday, 23 April 2019 2:00:42 ACST Luca Beltrame wrote:
In data lunedì 22 aprile 2019 15:37:21 CEST, Rodney Baker ha scritto:
It has been open since 23/01/17 (first reported in Kmail2 5.7.0) with apparently zero developer activity on it since it was reported.
While I don't know about the CPU usage (I can't reproduce it), I can tell you that unfortunately the mails not being displayed (if inline) is a limitation of the Qt engine used to display them (QWebEngine) which tops at a rather low value (I can't check which one, but it was a handful of Mb).
This issue ineeds to be handled in Qt, if fixable.
As an aside, you can't really "escalate" bugs. Best is to triage them to help developers find them: there are few PIM developers overall and the number of bugs in bugs.kde.org pretty large (including also duplicate, invalid, support requests mis-filed as bugs...).
Thanks, Luca. The frustrating thing is that using "view source" displays the message almost instantly (in my case, they're plain text messages, not html messages). I have no idea how to triage a bug like this, but I'll do what I can to help. I see now that it has been marked as a duplicate of #387061 (exactly how an older bug is a duplicate of a new one is slightly confusing), so at least that's progress. Hopefully it can be fixed. Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
participants (2)
-
Luca Beltrame -
Rodney Baker