Error "GPU process isn't usable".

[Xeo23]

[16871:16871:0227/183455.799412:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183456.185860:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183456.570101:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183456.984646:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183457.406136:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183457.881302:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183458.186283:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183458.501347:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183458.791993:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139 [16871:16871:0227/183458.792012:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye. [0227/183458.798735:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0227/183458.799067:ERROR:elf_dynamic_array_reader.h(64)] tag not found fish: Job 1, 'google-chrome-stable' terminated by signal SIGTRAP (Trace or breakpoint trap)

Facing this issue in opening spotify, brave, google chrome, vscode, obsidian, youtube music.. I can run all these with applications with --enable-features=UseOzonePlatform -ozone-platform=wayland flag. But spotify and chrome is not working at all.

I know this issue is not related to the Hyprdots project but any help would be appreciated.

[H1manshu-Soni]

Had same issue it fixes with setting ozone platform to Wayland but it's a hassle and pain in the back DK if it's related to latest update but it's really bugging me

[Xeo23]

Had same issue it fixes with setting ozone platform to Wayland but it's a hassle and pain in the back DK if it's related to latest update but it's really bugging me

Can you tell me how to do it. I couldn't find anything usefully elsewhere.

[H1manshu-Soni]

Had same issue it fixes with setting ozone platform to Wayland but it's a hassle and pain in the back DK if it's related to latest update but it's really bugging me

Can you tell me how to do it. I couldn't find anything usefully elsewhere.

I believe you have given me solution for this exact issue that I had with brave(rest follow soot). See #922

[Xeo23]

Had same issue it fixes with setting ozone platform to Wayland but it's a hassle and pain in the back DK if it's related to latest update but it's really bugging me

Can you tell me how to do it. I couldn't find anything usefully elsewhere.

I believe you have given me solution for this exact issue that I had with brave(rest follow soot). See #922

Yeah, I am just annoyed with chrome and spotify, for every other other application I made .desktop files with --enable-features=UseOzonePlatform -ozone-platform=wayland in the ~/.local/applications directory where it won't be overwritten even after updates.

I was able to run spotify with the same flag but every time I change the theme or wallpaper ( i.e run the wallbashspotify.sh) spotify gets automatically closed and I have to run it again to get new theme applied over it which is I think related to spicetify -q watch -s written in the wallbashspotify.sh script, which runs spicetify in monitor mode and reloads spotify automatically on theme change (but without the --enable-features=UseOzonePlatform -ozone-platform=wayland enabled) . It's so annoying.

And then this google chrome, only the flatpak version of chrome is running fine other than that I tried everything but its not working. And flatpak apps doesn't seems to follow wallbash theme very well either.

I posted this to see if someone has a better fix for it or am I stuck with these annoying bugs.

[kRHYME7]

@Xeo23 Please see spicetify docu to add custom flags. I added it here but did not work.

[Xeo23]

@kRHYME7 thanks for the information. I was able to get it working by adding spotify_launch_flags = --enable-features=UseOzonePlatform | -ozone-platform=wayland which is written here https://newreleases.io/project/github/spicetify/spicetify-cli/release/v1.0.0.

Still I can't figure out the issue with google-chrome.

[kRHYME7]

Good to hear!

Here's what the config look like if Spotify is not rendering(only transparent window)

And then this google chrome, only the flatpak version of chrome is running fine other than that I tried everything but its not working. And flatpak apps doesn't seems to follow wallbash theme very well either.

Can you elaborate more about this issue? IIRC no wallbash implementation for flatpak or Google Chrome yet.

For flatpak have you tried tweaking some apps using flatseal ?

Experience on google-chrome: ( Also applies to brave, thorium any chromium base browser or alike)

xwayland

wayland

I set this

then launch it with --disable-gpu dunno how to add it on the GUI

About the integration for hyprland. Maybe add windows rule for chrome.

Class for xwayland : Google-chrome Class for wayland : google-chrome

windowrulev2 = opacity 0.80 0.80,class:^(google-chrome)$
windowrulev2 = opacity 0.80 0.80,class:^(Google-chrome)$

To avoid this on Wayland Set this and use hotkeys to kill the window.

[2han9wen71an]

检查LIBVA_DRIVER_NAME是否为nvidia