Kostadin

I am getting something similar on Fedora Silverblue. Latest version of the application, got it from Flathub. `GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code36: GDBus.Error:org.gnome.Shell.ExtensionError: Unexpected response: Bad Request`

Same spam on Proton Experimental(bleeding-edge), no cyberengine tweaks, no raytracing enabled, only using `RADV_PERFTEST=sam` rx 6800, mesa-git, 6.0.10 kernel [vkd3d-proton.log](https://github.com/HansKristian-Work/vkd3d-proton/files/10143399/vkd3d-proton.log)

I have everything on max except Screen Space Reflections Quality, which is on high and everything in "Basic" is off and FOV is set to 90, 1080p. Also, it looks...

I managed to make it work on Gentoo by putting the libraries from `libamdenc-amdgpu-pro` and `libgl1-amdgpu-pro-oglp-dri` in a folder and then loading them with `LD_LIBRARY_PATH=(whatever the dir is) ffmpeg -i...

This is also reproducible with GNU's ld linker even if not using LTO if `LDFLAGS="-Wl,--no-undefined-version"` is set. FAILED: va/libva.so.2.2000.0 cc -o va/libva.so.2.2000.0 va/libva.so.2.2000.0.p/va.c.o va/libva.so.2.2000.0.p/va_compat.c.o va/libva.so.2.2000.0.p/va_str.c.o va/libva.so.2.2000.0.p/va_trace.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC...

Feel free to close this when [758](https://github.com/intel/libva/pull/732) or [732](https://github.com/intel/libva/pull/758) is merged.

I can reproduce this with Budgie 10.8.2 and GCC 14 ``` src/wm/budgie-wm.p/wm.c:7072:9: error: implicit declaration of function ‘meta_keybindings_set_custom_handler’ [-Wimplicit-function-declaration] 7072 | meta_keybindings_set_custom_handler ("panel-main-menu", _budgie_budgie_wm_launch_menu_meta_key_handler_func, g_object_ref (self), g_object_unref); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ```...

It seems like it is not possible to access the power tables in the ryzen_smu driver for my Ryzen 5 2600x (Pinnacle Ridge). Sorry for wasting your time.

I also had this but I uninstalled it the following way and it is working properly now: `flatpak --user uninstall de.shorsh.discord-screenaudio` `rm -rf ~/.var/app/de.shorsh.discord-screenaudio/` The flatpak command might or might...

Is this going to be fixed?