GNOME Bugzilla – Bug 777059
Wayland session login freezes with EasyScreenCast GNOME Shell extension
Last modified: 2017-07-10 00:13:51 UTC
How to reproduce: Tested in Fedora 25 with Intel Skylake: Install EasyScreenCast extension from extensions.gnome.org. Install gstreamer1-vaapi package. Logout and login into GNOME Wayland session. Wayland session login will freeze, mouse cursor won't move and only keeping a couple of seconds the power off button will trigger the ACPI power off to do a proper shutdown. Only needs to have gstreamer1-vaapi package installed; libva-*-driver is not required, will freeze anyways with or without it. Related EasyScreenCast issue: https://github.com/EasyScreenCast/EasyScreenCast/issues/118
Thanks for reporting this. Can you get some logs? GST_DEBUG=*:2,vaapi*:5 Does it works within a X session?
With the wayland Session, no logs are written while initializing the extension. With the X Session (which works), only the first couple of lines are relevant, as the other lines only work when the libva driver is installed, and fails even without the driver: 0:00:00.508246899 2233 0x561cbbabdd30 INFO vaapi gstvaapidisplay.c:120:libgstvaapi_init_once: gstreamer-vaapi version 0:00:00.513776864 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: calculated pixel aspect ratio: 0.999820 0:00:00.607006193 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:942:gst_vaapi_display_create_unlocked: VA-API version 0.39 0:00:00.607119404 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:538:ensure_profiles: 14 profiles 0:00:00.607143354 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileMPEG2Simple 0:00:00.607162329 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileMPEG2Main 0:00:00.607176360 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileH264ConstrainedBaseline 0:00:00.607191101 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileH264Main 0:00:00.607204851 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileH264High 0:00:00.607218381 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileH264MultiviewHigh 0:00:00.607232444 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileH264StereoHigh 0:00:00.607246526 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Simple 0:00:00.607259704 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Main 0:00:00.607273179 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Advanced 0:00:00.607289839 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileJPEGBaseline 0:00:00.607312844 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: VAProfileVP8Version0_3 0:00:00.607333186 2233 0x561cbbabdd30 DEBUG vaapi gstvaapidisplay.c:545:ensure_profiles: <unknown>
(In reply to Francisco de la Peña from comment #2) > With the wayland Session, no logs are written while initializing the > extension. It is hard to figure out what is happening with no means to trace the problem. > > With the X Session (which works), only the first couple of lines are > relevant, as the other lines only work when the libva driver is installed, > and fails even without the driver: I don't now follow these lines. What do you mean? > > 0:00:00.508246899 2233 0x561cbbabdd30 INFO vaapi > gstvaapidisplay.c:120:libgstvaapi_init_once: gstreamer-vaapi version > 0:00:00.513776864 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: > calculated pixel aspect ratio: 0.999820 > 0:00:00.607006193 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:942:gst_vaapi_display_create_unlocked: VA-API version 0.39 > 0:00:00.607119404 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:538:ensure_profiles: 14 profiles > 0:00:00.607143354 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileMPEG2Simple > 0:00:00.607162329 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileMPEG2Main > 0:00:00.607176360 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileH264ConstrainedBaseline > 0:00:00.607191101 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileH264Main > 0:00:00.607204851 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileH264High > 0:00:00.607218381 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileH264MultiviewHigh > 0:00:00.607232444 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileH264StereoHigh > 0:00:00.607246526 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Simple > 0:00:00.607259704 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Main > 0:00:00.607273179 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileVC1Advanced > 0:00:00.607289839 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileJPEGBaseline > 0:00:00.607312844 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: VAProfileVP8Version0_3 > 0:00:00.607333186 2233 0x561cbbabdd30 DEBUG vaapi > gstvaapidisplay.c:545:ensure_profiles: <unknown>
> It is hard to figure out what is happening with no means to trace the problem. Unfortunately, yes. I tried with GST_DEBUG_FILE in /etc/profile.d/ to catch these lines, but only X session writes stuff because it does not crash with it. > I don't now follow these lines. What do you mean? The EasyScreenCast extension initializes on session startup and writes some output to the GST_DEBUG_FILE. When I remove the libva-*-driver file, it still freezes in the Wayland session in the same way and writes nothing there. In the X session the extension still loads as usual and it writes this in the log, where it shows the same first couple of function calls: 0:00:00.005270151 7301 0x55fcd4b93d30 INFO vaapi gstvaapidisplay.c:120:libgstvaapi_init_once: gstreamer-vaapi version 0:00:00.011254250 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: calculated pixel aspect ratio: 0.999820 0:00:00.011690649 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapiutils.c:53:vaapi_check_status: vaInitialize(): unknown libva error 0:00:00.015378077 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: calculated pixel aspect ratio: 0.999820 0:00:00.015678702 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapiutils.c:53:vaapi_check_status: vaInitialize(): unknown libva error 0:00:00.016429171 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: calculated pixel aspect ratio: 1.000000 0:00:00.016574501 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapiutils.c:53:vaapi_check_status: vaInitialize(): unknown libva error 0:00:00.017145166 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapidisplay.c:802:gst_vaapi_display_calculate_pixel_aspect_ratio: calculated pixel aspect ratio: 1.000000 0:00:00.017561418 7301 0x55fcd4b93d30 DEBUG vaapi gstvaapiutils.c:53:vaapi_check_status: vaInitialize(): unknown libva error 0:00:00.017585610 7301 0x55fcd4b93d30 ERROR default gstvaapi.c:234:plugin_init: Cannot create a VA display journalctl does not catch any relevant line neither. Maybe is still a Wayland or GNOME Shell issue, I'm going to retry the next week to get more details. In any case this issue is easy to reproduce by following the mentioned steps if anyone want to take a try. Other gst based apps such totem work properly in my hardware with Wayland and libva.
*** This bug has been marked as a duplicate of bug 776041 ***