KDE Pim Apps fail on Wayland/Tumbleweed/Plasma6
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 rodney.baker@outlook.com.au ==========================================================================================================
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.
[...] BTW, the same thing happens if I try to run Kontact or akonadiconsole, but all other KDE apps that I've tried (and non-KDE apps as well) seem to be perfectly happy. It appears to be limited to only KDEPim apps. And not that it probably matters, but it's a GTX1080Ti and the same error was happening with the 550.54.14 drivers as well. -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
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 rodney.baker@outlook.com.au ==========================================================================================================
On Saturday, 6 April 2024 00:08:59 ACDT Rodney Baker wrote:
On Friday, 5 April 2024 23:38:30 ACDT Rodney Baker wrote: [...]
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.
If I run vainfo under Wayland I get: ~ $ 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 The exact text of the error dialog after trying to run Kmail under Wayland and then going back to X11 is: "The Email progam encountered a fatal error and will terminate now. The error was: Timeout trying to get lock." Regards, -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
On Saturday, 6 April 2024 00:47:18 ACDT Rodney Baker wrote:
On Saturday, 6 April 2024 00:08:59 ACDT Rodney Baker wrote:
On Friday, 5 April 2024 23:38:30 ACDT Rodney Baker wrote: [...]
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.
If I run vainfo under Wayland I get:
~ $ 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
The exact text of the error dialog after trying to run Kmail under Wayland and then going back to X11 is:
"The Email progam encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
Regards,
The timeout may be a race condition - it does not appear to occur when running Kmail under gdb. -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
On Saturday, 6 April 2024 15:41:20 ACDT Rodney Baker wrote:
On Saturday, 6 April 2024 00:47:18 ACDT Rodney Baker wrote:
On Saturday, 6 April 2024 00:08:59 ACDT Rodney Baker wrote:
On Friday, 5 April 2024 23:38:30 ACDT Rodney Baker wrote: [...]
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.
If I run vainfo under Wayland I get:
~ $ 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
The exact text of the error dialog after trying to run Kmail under Wayland and then going back to X11 is:
"The Email progam encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
Regards,
The timeout may be a race condition - it does not appear to occur when running Kmail under gdb.
It doesn't crash when running it under gdb in Wayland with "gdb --args kmail --platform xcb" either... -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
In data venerdì 5 aprile 2024 15:08:30 CEST, Rodney Baker ha scritto:
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,
I can confirm this for a laptop with Kontact in autostart and Tumbleweed. The latest update fixed this a bit, but Wayland in TW is as far as I am concerned unusable with multiple showstoppers (of which kmail is only one aspect, e.g. the nitrokey does not work because the app does not work in wayland etc. ) Well, I had, blinking windows, crashing or vanishing Kontakt, multiple instances opening, impossibility to close some of them, some would close other with them..... currently I am with X11 and it works. I do not think the current implementation of Plasma is a viable thing for productive machines. Do not think you issue is Nvidia or connected. Still on my laptop I am using IMAP, on my PC POP and while POP works, on the laptop the IMAP seems broken because it creates duplicates, sometimes twice int he same session of KDE.
On Saturday, 6 April 2024 03:39:46 ACDT Stakanov wrote:
In data venerdì 5 aprile 2024 15:08:30 CEST, Rodney Baker ha scritto:
Hi all,
[...]
I can confirm this for a laptop with Kontact in autostart and Tumbleweed. The latest update fixed this a bit, but Wayland in TW is as far as I am concerned unusable with multiple showstoppers (of which kmail is only one aspect, e.g. the nitrokey does not work because the app does not work in wayland etc. )
Well, I had, blinking windows, crashing or vanishing Kontakt, multiple instances opening, impossibility to close some of them, some would close other with them.....
currently I am with X11 and it works. I do not think the current implementation of Plasma is a viable thing for productive machines. Do not think you issue is Nvidia or connected.
Still on my laptop I am using IMAP, on my PC POP and while POP works, on the laptop the IMAP seems broken because it creates duplicates, sometimes twice int he same session of KDE.
Cheers, glad it's not just me. I've added the results from my system to Bugzilla (Bug 1222178) and increased the priority and severity. Regards, -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
On Saturday, 6 April 2024 13:51:21 ACST Rodney Baker wrote:
On Saturday, 6 April 2024 03:39:46 ACDT Stakanov wrote:
In data venerdì 5 aprile 2024 15:08:30 CEST, Rodney Baker ha scritto:
Hi all,
[...]
I can confirm this for a laptop with Kontact in autostart and Tumbleweed. The latest update fixed this a bit, but Wayland in TW is as far as I am concerned unusable with multiple showstoppers (of which kmail is only one aspect, e.g. the nitrokey does not work because the app does not work in wayland etc. )
Well, I had, blinking windows, crashing or vanishing Kontakt, multiple instances opening, impossibility to close some of them, some would close other with them.....
currently I am with X11 and it works. I do not think the current implementation of Plasma is a viable thing for productive machines. Do not think you issue is Nvidia or connected.
Still on my laptop I am using IMAP, on my PC POP and while POP works, on the laptop the IMAP seems broken because it creates duplicates, sometimes twice int he same session of KDE.
Cheers, glad it's not just me. I've added the results from my system to Bugzilla (Bug 1222178) and increased the priority and severity.
Regards,
Seems to be fixed with the 20240409 snapshot. -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
participants (2)
-
Rodney Baker -
Stakanov