Bug 502799

Summary: Email message detail view is blank
Product: [Applications] kmail2 Reporter: leo5t
Component: UIAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella
Priority: NOR    
Version First Reported In: 6.3.90   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Message preview is empty

Description leo5t 2025-04-14 17:13:16 UTC
Created attachment 180260 [details]
Message preview is empty

SUMMARY
When selecting  an email message the detail view remains blank

STEPS TO REPRODUCE
1.  Select an email message

OBSERVED RESULT
The detail view is blank

EXPECTED RESULT
To see the message body preview

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
System log shows these entries:
14.04.2025 19:02:29:622	kontact	Backend texture is not a Vulkan texture.
14.04.2025 19:02:29:622	kontact	Compositor returned null texture
Comment 1 leo5t 2025-04-27 08:03:01 UTC
I would like to add an information. While the email body is totally blank, moving the mouse over the blank area changes the cursor appearence when it is over a link, and if I click the link it opens. 
I see you changed priority of this bug. I would not consider normal priority, as being unable to read the email makes an email client useless.
Comment 2 Antonio Rojas 2025-05-01 15:56:32 UTC

*** This bug has been marked as a duplicate of bug 502736 ***
Comment 3 leo5t 2025-05-15 20:15:29 UTC
It seems that after having being fixed, the problem is here again after the latest update:

KMail version: 25.04.1-1
Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: GeForce GT 440/PCIe/SSE2

I reported also at https://bugs.kde.org/show_bug.cgi?id=502736 because this bug was marked as its duplicate, although descriptions seem different