Blank screen on Fedora 35 running on nouveau driver

[ocosta]

Spotify was running just fine on Fedora 34, but this is not the case anymore with Fedor 35. All I see is a blank screen. If I run it from the console I get this:

flatpak run com.spotify.Client 
/app/extra/bin/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/bin/spotify)
[spotifywm] attached to spotify
/app/extra/share/spotify/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/share/spotify/spotify)
/app/extra/share/spotify/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/share/spotify/spotify)
[spotifywm] attached to spotify
[spotifywm] attached to spotify
Gtk-Message: 22:57:33.052: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:33.052: Failed to load module "pk-gtk-module"
Gtk-Message: 22:57:33.052: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:33.052: Failed to load module "pk-gtk-module"
/proc/self/exe: /app/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[spotifywm] attached to spotify
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

[TingPing]

These aren't really actionable issues. Spotify, and Bitwarden, use Chromium which has expectations about OpenGL working.

So I would say your issues are entirely between Chromium <-> Nouveau. And some changes will need to happen there.

If you just wait its entirely possible it gets fixed upstream by itself with future updates.

[ocosta]

Thanks for the info, I guess that makes sense. I would happily file this upstream, but I'm afraid I probably won't be able to provide much info for them, unless there is any specific tests I could do. Any tips? Otherwise, I guess I'll just have to wait indeed...

[TingPing]

Yeah, unless you are very familiar with Chromium it would be very hard to track down.

[ocosta]

Mmmh... so it's not exclusive to nouveau. Maybe this will attract more attention from Chromium devs?

[hiredman]

Sorry for the noise, I thought I deleted my comment. When I left Spotify open long enough(enough to find this issue and leave a comment) eventually the ui rendered, and everything seems fine now.

…

On Tue, Nov 16, 2021, 12:41 André Costa ***@***.***> wrote: Mmmh... so it's not exclusive to nouveau. Maybe this will attract more attention from Chromium devs? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#187 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIY4XMV2OMG7KTOUGP5MDUMK6WFANCNFSM5H6BXOSA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[ocosta]

Thanks for the clarification. Well, I got some news as well: installed nvidia's proprietary driver (from Negativo17.org), and now both Spotify and Bitwarden are working again, with no delays -- but Telegram crashes right from the start, claiming "Open GL issues". It automatically disabled "OpenGL rendering for media" setting. So, it does seem to be related to nouveau somehow. But the Telegram issue was sort of a plot-twist...

[Zlopez]

As Fedora 35 is no longer even supported by Fedora is this still relevant?