Black screen with Wayland (Sway) #165
Labels
bug
Something isn't working
Comments
|
Works fine for me with the flatpak (flathub stable). Sway, Arch, Radeon Mesa drivers. Could you try out the flatpak version? I do have mpv-shim (same install source) stopped working for me some time ago though. |
|
This does appear to work, although I don't know why it'd magically work through Flatpak and not through proper Arch packages. |
|
Flatpak comes with its own version of mesa, it could be related. X doesn't use EGL, so if your version of mesa has an issue with that, it could cause the problem. Using an older mesa git, maybe? Alternatively, it could be config-related. |
|
I'm experiencing this issue as well on a brand new Arch install. Same error output and black screen when launching the AUR pkg. Flatpak version launches after a while but requires hardware decoding disabled to not crash when attempting playback, and takes 30+ seconds to start playing a file. When launching the Flatpak pkg from the terminal I'm met with |
|
I recall getting that same error, although it didn't seem to cause me any issues. Out of curiosity, are you using proprietary Nvidia graphics? |
|
I was indeed running Nvidia's propriertary drivers. I could not resolve the issue and reverted back to X11 so I won't be of much use troubleshooting this further. |
|
Having the same issue here. (Also nvidia, and have it under plasma, gnome, sway, wayfire). For now just running it in xwayland. Flatpak works fine but it's missing any sort of decoration whatsoever. Cursor, title bar etc all missing. Maybe the flatpak is built differently and doesn't use QT? |
|
I'm having the same issue. Running with Terminal output with My logfile:
|
|
Edit: sorry, I had assumed this was the issue about flatpak (that's #90). I removed mentions of it below. As you are running outside of Flatpak, I'm assuming you run on a Wayland-compatible DE/compositor (sway?). @zjeffer Could you provide more details on your system?
Just to clarify, though you probably know this, if you want to default to XWayland (on a Wayland compositor) with an environment variable, you need to set |
I know, but I'm trying to make it work with wayland natively. I'm running You mentioned mesa, here are the packages I have installed with mesa in the title or description: |
|
I can't say much, especially as I don't have any nvidia GPU, though trying another driver version would be my top guess. The error seems to come from here, probably propagated from a few lines above. Though I am not sure what version jellyfin-media-player uses. Could be an issue with chromium or qt5webengine: danvd/wlroots-eglstreams#5 (comment) Perhaps specifically with hybrid graphics configurations (though weird if you disabled it in your bios): qutebrowser/qutebrowser#7584 It might get fixed if jellyfin-media-player upgrades qtwebengine to version 6.5+ Also similar issue here, which links to a workaround you could try (rather, a variant providing nvidia's json file). |
The qt6 branch starts without issues, but has a different issue with playing video, so it is not usable yet. Using the master branch, I tried the workaround with the json file, by running with this environment variable: but while it boots fine, it screws up the UI, making it unusable:
If I resize the window horizontally past a certain point, or I maximize or fullscreen, the issue is gone and the UI is back to normal and the app is usable. EDIT: sadly, playing video looks very bad: lots of color banding and general blurryness when using the 50_mesa.json file. |
|
@lilithium-hydride Is this issue still valid? I had similar problems and with latest version of NVIDIA drivers they finally disappeared. (see flathub/com.github.iwalton3.jellyfin-media-player#7 for details) |
|
@Orhideous My nvidia packages are on version I think maybe it's fixed for you because something changed in the flatpak? I don't use flatpak, I use the AUR package which compiles it from scratch. Maybe the flatpak now forces the platform to xcb instead of wayland? |
|
Bump, black screen + errors still a problem on GNOME Wayland on Fedora 38, NVIDIA driver 535.113.01. Built from latest source and latest stable version. |
Having the same issue, GNOME Wayland, Fedora 38, NVIDIA driver 535.113.01. Installed from flathub. However |
|
Same issue:
|
|
Same issue:
|
|
This is still an issue for me and the
I'm running the Flathub version on a relatively clean install of Fedora 39 and the latest Nvidia drivers (545.X). |
|
Same issue here. Log |
|
Fixed by using this libva patch intel/libva#790. |
|
I had installed a bunch of libva stuff and then started to experience this. What fixed it for me was removing |
Might be related, but my distro recently moved from X11 to Wayland Works
Partially works (sometimes)Not a black screen but still outputs 100s of the error log lines
Does not work
|
|
Same issue: |
|
+1 on this (info from kde info centre) |
|
+1 Arch Linux |
|
Same issue on NixOS.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
jellyfinmediaplayerdisplays a purely black screen upon application launch and generates a bunch of errors.To Reproduce
Steps to reproduce the behavior:
jellyfinmediaplayeror open Jellyfin Media Player from your preferred launcher.Expected behavior
The application displays the typical screen, either server selection or the server home page.
Screenshots
I can add them if desired, but it's literally just
#000000across the entire window. No menu bar, either.Desktop (please complete the following information):
jellyfinmediaplayer 1.6.1,Jellyfin.Server 10.8.0.0-gitpackages.Additional context
I'm using Sway on an NVIDIA GPU, driver version
495.44. It works perfectly on i3, and if I force XWayland withenv -u WAYLAND_DISPLAY jellyfinmediaplayer, it (surprisingly) seems to work just as well as on i3 (apart from some horizontal flickering chunks near the top of the window).Log File
jellyfinmediaplayer.log
The text was updated successfully, but these errors were encountered: