Re: KDE Pim Apps fail on Wayland/Tumbleweed/Plasma6

Rodney Baker <[email protected]> Sat, 06 Apr 2024 00:08:59 +1030
Newsgroups gmane.linux.suse.kde
Message-ID <MEYP282MB3323C379C765378A79EFCD4FBC032@MEYP282MB3323.AUSP282.PROD.OUTLOOK.COM>
On Friday, 5 April 2024 23:38:30 ACDT Rodney Baker wrote:
> 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,

Running vainfo shows:

~ $ vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.20.0
libva error: vaGetDriverNames() failed with unknown libva error
libva info: User environment variable requested driver 'vdpau'
libva info: Trying to open /usr/lib64/dri/vdpau_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.20 (libva 2.20.1)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG4Simple            : VAEntrypointVLD
      VAProfileMPEG4AdvancedSimple    : VAEntrypointVLD
      <unknown profile>               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD

Seems related but I don't know what's causing the failure. 

~ $ ls -l /usr/lib64/*vdpau*
lrwxrwxrwx 1 root root    31 Apr  4 18:26 /usr/lib64/libvdpau_nvidia.so -> 
vdpau/libvdpau_nvidia.so.550.67
lrwxrwxrwx 1 root root    13 Mar  1 20:47 /usr/lib64/libvdpau.so -> 
libvdpau.so.1
lrwxrwxrwx 1 root root    17 Mar  1 20:47 /usr/lib64/libvdpau.so.1 -> 
libvdpau.so.1.0.0
-rwxr-xr-x 1 root root 18408 Mar  1 20:47 /usr/lib64/libvdpau.so.1.0.0

No idea if any of that is relevant or not. 

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