Bug 1807183 - Email content is not displayed
Summary: Email content is not displayed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grantlee-qt5
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-25 18:33 UTC by nucleo
Modified: 2021-05-25 15:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 15:44:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fix missing dependency in grantlee-qt5.spec (396 bytes, patch)
2020-02-28 23:42 UTC, nucleo
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 418192 0 NOR RESOLVED Email content is not displayed in Fedora 32 2020-03-02 21:40:50 UTC

Description nucleo 2020-02-25 18:33:53 UTC
Description of problem:
Email content from gmail imap caacount is not displayed.

Version-Release number of selected component (if applicable):
kmail-19.12.2-1.fc32.x86_64

How reproducible:
In every email.

Steps to Reproduce:
1. Start live image Fedora-KDE-Live-x86_64-32-20200224.n.0.iso from https://dl.fedoraproject.org/pub/fedora/linux/development/32/Spins/x86_64/iso/
2. Add in kmail gmail IMAP account (server imap.gmail.com, port 993 SSL/TLS, clear text authentification)
3. Open any email from Inbox folder.


Actual results:
Only Subject, From, To, Date shown but no email contents.

Comment 1 nucleo 2020-02-28 23:21:33 UTC
When kmail started in konsole there is error message displayed after opening emails

grantlee.template: "Plugin library 'grantlee_scriptabletags' not found."
org.kde.pim.messageviewer: "Plugin library 'grantlee_scriptabletags' not found." . Searched in subdir mimetreeparser/themes/default in these locations ("/home/liveuser/.local/share", "/usr/share/kde-settings/kde-profile/default/share", "/usr/local/share", "/usr/share")

Comment 2 nucleo 2020-02-28 23:42:41 UTC
Created attachment 1666504 [details]
fix missing dependency in grantlee-qt5.spec

Emails fixed after fixing missing dependency in grantlee-qt5 5.2.

Comment 3 nucleo 2020-03-02 21:45:32 UTC
Bug fixed after update to grantlee-qt5-5.2.0-5.fc32.x86_64.rpm

Comment 4 Fedora Program Management 2021-04-29 16:13:05 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-05-25 15:44:08 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.