Bug 1222178

I can also confirm this, using a NVIDIA RTX 4070 Laptop GPU.

Even on a fresh Tumbleweed install, KMail and Kontact freeze upon starting immediately. 

What I observed though is, that this is only happening for me inside a Wayland session. On X11, both programs are working fine.

Also: on the X11 Session I'm receiving an authorization request from Akonadi for kwallet, on Wayland, nothing happens.

I should have mentioned that I'm indeed using wayland on both machines. I would suspect this issue to be Qt 6 and Nvidia related, for several Qt 6 packages got updated in 20240328 snapshot.

Confirmed here also - running KMail under X11 works, as long as it has not been started under Wayland first. 

If I start KMail in a Plasma Wayland session, it hangs indefinitely. Logging out and then logging into a Plasma X11 session and starting KMail results in a segfault and crash. 

Running KMail from Konsole results in:

[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 dialog stating, "The Email program has encountered a fatal error and will now close. The error was: Timeout trying to get lock."

Running vainfo under X11:

~ $ 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

Running vainfo under Wayland:

~ $ vainfo
Trying display: wayland
libva info: VA-API version 1.20.0
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 error: /usr/lib64/dri/vdpau_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Running KMail under Wayland as "kmail --platform xcb" gives: 

[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
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

Can you try with `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu kmail` or `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu kontact`

(In reply to Christophe Marin from comment #4)
> Can you try with `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu kmail` or
> `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu kontact`

Running `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail` indeed worked. KMail got responsive again.

Ok, I guess that's https://bugreports.qt.io/browse/QTBUG-124174 then

Running `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" kmail` solves the non-responsive startup but does not resolve the "Timeout trying to get lock" issue noted in comment #3 below. I guess that's a different bug then? I do have a full gdb backtrace and valgrind log for that one - should I raise a separate issue here or report upstream?

I should mention that I've had kmail work sometimes under Wayland with the parameter --platform xcb as long as KMail is the FIRST application started after the desktop session loads. If any other application has been loaded first, it crashes every time.

Good news is that my problem got fixed in 20240409 snapshot, which brought Qt 6.7 update. Now KMail can be normally opened and used without `QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"` variable.

Does anyone in this discussion still got the problem? I would like to mark it as FIXED if not. It turned out to be solved by a Qt update.

Works for me now too.