KDE Pim Apps fail on Wayland/Tumbleweed/Plasma6

Rodney Baker <[email protected]> Fri, 05 Apr 2024 23:38:30 +1030
Newsgroups gmane.linux.suse.kde
Message-ID <MEYP282MB3323A7662475DD012AD6A5E5BC032@MEYP282MB3323.AUSP282.PROD.OUTLOOK.COM>
Hi all,

Ever since the Tumbleweed snapshot containing the liblzma fix/rollback, Kmail 
is refusing to run under Wayland/Plasma 6 (running Nvidia GTX1080 with driver 
version 550.67 from the Nvidia website). 

If I log into a Plasma X11 session immediately after boot, or if I start a 
Plasma Wayland session and then logout before starting Kmail and start a 
Plasma X11 session, Kmail works fine. 

If I attempt to run Kmail under Plasma Wayland, the window appears and 
sometimes has the folder list populated, but it hangs indefinitely and shows 
"Starting" in the status line. Clicking on it results in the unresponsive app 
dialog and the only option is to kill it. 

If I then log out and log into a Plasma X11 session without rebooting, Kmail 
starts but after 2 minutes a dialog appears that says, "The application has 
experienced a critical error and will now close" (or words to that effect). 

Running it from a command line produces the following: 

[13801:14241:0405/231901.115472:ERROR:vaapi_wrapper.cc(1319)]  
vaQuerySurfaceAttributes failed, VA error: invalid parameter
[13801:14241:0405/231901.115495:ERROR:vaapi_wrapper.cc(1267)] 
FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint 
VAEntrypointVLD
[13801:14241:0405/231901.115504:ERROR:vaapi_wrapper.cc(1319)] 
vaQuerySurfaceAttributes failed, VA error: invalid parameter
[13801:14241:0405/231901.115510:ERROR:vaapi_wrapper.cc(1267)] 
FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint 
VAEntrypointVLD

Followed by a segfault.


If I reboot and log straight into a Plasma X11 session it works fine again, 
until I next try to run it under Wayland.

I also tried running it under Wayland from a Konsole session using 'kmail --
platform xcb', which worked for 2 mins and then produced exactly the same 
error, followed by:

src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or 
not supported format: 808530000

src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or 
not supported format: 808530000

src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or 
not supported format: 808530000

src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or 
not supported format: 808530000

src/gbm_drv_common.c:130: GBM-DRV error (get_bytes_per_component): Unknown or 
not supported format: 808530000

And the same "Critical error" dialog. 

It has worked fine under Wayland for months, before and after the upgrade to 
Plasma 6 - it's only in the last week or so that it has begun to fail. 

Any clues where to look next? 

Regards,

-- 
==========================================================================================================
Rodney Baker
[email protected]
==========================================================================================================