Bug 438345 - Contents load as Blank Page in Wayland - Kmail and Akregator
Summary: Contents load as Blank Page in Wayland - Kmail and Akregator
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: mail (other bugs)
Version First Reported In: 5.16.3
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 397825 427584 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-06-09 17:43 UTC by Jebin
Modified: 2025-09-09 19:36 UTC (History)
16 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kmail black screen (148.78 KB, image/png)
2021-06-09 17:43 UTC, Jebin
Details
Akgregator black screen (193.03 KB, image/png)
2021-06-09 17:43 UTC, Jebin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jebin 2021-06-09 17:43:22 UTC
Created attachment 139152 [details]
kmail black screen

SUMMARY
I recently switched to wayland in Fedora 34. Both Kmail and Akgregator doesn't work properly under Wayland. They both load as black screens. Actually both of them load intially after a long waiting time but doesn't work if we switch between them.


STEPS TO REPRODUCE
1. Open Kontact suite in wayland session.
2. Open Kmail or Akgregator within it (HTML content)
3. It will display black screen. (Also the mail list will be unusable until it loads.

OBSERVED RESULT
Black screen. Refer attachments.

EXPECTED RESULT
Load normally, similar to X11

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.6-300.fc34.x86_64
OS Type: 64-bit
Graphics Platform: Wayland


ADDITIONAL INFORMATION
Comment 1 Jebin 2021-06-09 17:43:59 UTC
Created attachment 139153 [details]
Akgregator black screen
Comment 2 bugzy 2021-07-09 16:09:24 UTC
*** Bug 427584 has been marked as a duplicate of this bug. ***
Comment 3 bugzy 2021-07-09 16:10:15 UTC
*** Bug 397825 has been marked as a duplicate of this bug. ***
Comment 4 Paul Gover 2021-08-06 08:20:28 UTC
I'm also getting this, on Gentoo, with:
Plasma 5.21.5
kmail 20.12.3
kwayland 5.82.0
qtwayland 5.15.2
kernel 5.13.7
amdgpu
Comment 5 Damian C 2022-06-24 06:41:18 UTC
Same, but with white screen instead of black. Presumably due to theming.

Operating System: Arch Linux
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.18.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2
Comment 6 Paul Gover 2022-06-24 10:56:25 UTC
(In reply to Paul Gover from comment #4)
> I'm also getting this, on Gentoo, with:
> Plasma 5.21.5
> kmail 20.12.3
> kwayland 5.82.0
> qtwayland 5.15.2
> kernel 5.13.7
> amdgpu

----
Now working OK!

Plasma 5.24.5
kmail 21.12.3
qtwayland 5.15.4
kernel 5.18.6
Comment 7 Damian C 2022-06-24 14:17:09 UTC
(In reply to Damian C from comment #5)
> Same, but with white screen instead of black. Presumably due to theming.
> 
> Operating System: Arch Linux
> KDE Plasma Version: 5.25.1
> KDE Frameworks Version: 5.95.0
> Qt Version: 5.15.5
> Kernel Version: 5.18.6-zen1-1-zen (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
> Memory: 15.5 GiB of RAM
> Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

I must clarify, that unlike the bug reporter, I do not get the same blank screen with the Feeds (Akregator), and the messages do load if I double click to open them in a new window. But I did not see them loading even after a while.
The button in the middle of the panes, to switch from HTML to Plain Text, is also unresponsive using wayland, it simply does nothing.
Comment 8 Filip Brcic 2022-12-27 18:14:30 UTC
I get the blank white screen for html mail as well. But if I open the mail in a new window everything works as expected.

Operating System: NixOS 22.11
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.10-lqx1
Graphics Platform: Wayland
Processors: AMD Ryzen 5 3600X (12) @ 3.800GHz
Memory:  32 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060 SUPER
Comment 9 Adam Borsos 2023-04-11 08:49:38 UTC
QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing" works me as a workaround, so the issue seems to be HW accel related

(Operating System: Gentoo Linux 2.13
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.19-gentoo-x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2)
Comment 10 Damian C 2023-04-11 09:22:01 UTC
(In reply to Adam Borsos from comment #9)
> QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing" works me as a
> workaround, so the issue seems to be HW accel related
> 
> (Operating System: Gentoo Linux 2.13
> KDE Plasma Version: 5.27.4
> KDE Frameworks Version: 5.104.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.19-gentoo-x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
> Memory: 31.2 GiB of RAM
> Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2)

This works for me as well! Also works for the news feed.
Comment 11 floppy5.25 2025-04-09 21:28:27 UTC
This bug did not exist on Arch Linux, Wayland, Radeon graphics on version qt6-webengine 6.8.3-1 but started happening after an upgrade to 6.9.0-3
It affects not only Kontact, Kmail, Akregator but also Konqueror and Falkon (or anyhing that uses the webengine I suspect)
Bug seems not to be on Intel graphics.
I can confirm that disabling GPU compositing as stated above is a workaround.
Comment 12 Soumyadeep Ghosh 2025-07-01 06:54:12 UTC
I can confirm this issue too, happening with QML WebEngineView + Wayland. The C++ variant works fine though. I am on KDE Neon, Qt 6.9.0
Comment 13 piedro 2025-09-09 11:08:52 UTC
On OpenSUSE Tumbleweed this happened just yesterday - it's really disruptive. 

It issue is related to the latest qt6-webengine 6.9.2-1.1 on wayland (it seems). 
For me it's hard to deal with as everything in KDE seems to depend on qt6-webengine. This is on: 
 
Operating System: openSUSE Tumbleweed 20250905
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 32 GiB of RAM (31.1 GiB usable)
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS

If hardware acceleration in wayland is the culprit how can this workaround be used for Kmail but not for the whole desktop environment? 

Thanks.
p.
Comment 14 piedro 2025-09-09 11:14:01 UTC
Sorry. My bad... - just using the workaround environment variable for starting single programs like kmail seems to work!
Comment 15 David de Cos 2025-09-09 14:33:45 UTC
(In reply to floppy5.25 from comment #11)
> Bug seems not to be on Intel graphics.

I've got a single integrated Intel card and the bug happens in my system too:

Operating System: openSUSE Tumbleweed 20250908
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.5-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: Intel® HD Graphics 520

Fortunately, disabling GPU compositing works here too.
Comment 16 Florian 2025-09-09 19:36:58 UTC
(In reply to piedro from comment #13)
> On OpenSUSE Tumbleweed this happened just yesterday - it's really
> disruptive. 
> 
> It issue is related to the latest qt6-webengine 6.9.2-1.1 on wayland (it
> seems). 
> For me it's hard to deal with as everything in KDE seems to depend on
> qt6-webengine. This is on: 
>  
> Operating System: openSUSE Tumbleweed 20250905
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.2
> Kernel Version: 6.16.3-1-default (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
> Memory: 32 GiB of RAM (31.1 GiB usable)
> Graphics Processor: AMD Radeon RX 6700 XT
> Manufacturer: ASUS
> 
> If hardware acceleration in wayland is the culprit how can this workaround
> be used for Kmail but not for the whole desktop environment? 
> 
> Thanks.
> p.

Confirmed - I've the same problem since today on my Tumbleweed installation (with AMD Radeon RX7700)