Stuck in full screen #94
Comments
|
Search for "jellyfinmediaplayer.conf" file in C drive and open the file in notepad when you find the file. Find the "forceFSScreen": |
|
Are there any fixes for this? It still occurs in the latest stable version (v1.6.1). |
|
Not sure if I have the same problem since it's always Fullscreen for me, except for the Windows Taskbar at the bottom. Is there supposed to be be way of exiting the app (traditionally via an X in the upper right corner in Windows)? Alt+F4 or right clicking the taskbar entry and clicking Close Window seem like an odd thing. |
|
I'm having the same issue. Jellyfin Server 1.7.7
The fullscreen checkbox seems to automatically revert to being checked (forceFSScreen:true) After trying all the above mentioned possibilities the log show this: The only solution is the one that @mekemahmud suggested, which is to edit the |
|
Well there really is just code in here that sets the view to fullscreen on Windows in some conditions. Not sure why I have never had it happen in testing... #ifdef Q_OS_WIN32
if (visibility == QWindow::Windowed)
{
QScreen* realScreen = findCurrentScreen();
if (realScreen && realScreen->geometry() == geometry())
{
QLOG_WARN() << "winging it!";
setScreen(realScreen);
setVisibility(QWindow::FullScreen);
return;
}
}
#endif |
|
This change will be in this next hotfix. Please let me know if this fixes the issue. |
|
Seems fixed. Everything I've tried to break it fails to work, and I'm able to pop in and out of fullscreen using any of the shortcuts even having closed the app while in fullscreen. |
|
Emm I'm still get the same problem on Windown 11 with Jellyfin Media Player version 1.7.1, even after I uninstalled it and removed all the config files in %APPDATA% and reinstalled it. It always open in fullscreen mode, and alt+enter does nothing, and the titlebar is missing. |
I've found out what the problem is. It may be related to the scaling ratio in windows setting. My laptop has a 2k display so I use 150% scaling for display. And jellyfin media player could not handle this situation correctly, making the titlebar out of the display so I misunderstood that it was stuck in fullscreen mode. I reset to 100% scaling, resize the jellyfin window and then change scaling back to 150%, and finallly it worked perfectly. |
I've found out what the problem is. It may be related to the scaling ratio in windows setting. My laptop has a 2k display so I use 150% scaling for display. And jellyfin media player could not handle this situation correctly, making the titlebar out of the display so I misunderstood that it was stuck in fullscreen mode. I reset to 100% scaling, resize the jellyfin window and then change scaling back to 150%, and finally it worked perfectly. |
|
Can confirm this is actually a scaling issue. Happened to me on windows 11 (100% scaling 2K) changed scaling to 125% the bar showed up maxed the window then scaled back to 100% all good now. First time i ever get this issue nothing changed just randomly after waking up from sleep. |
Completely different issue. This issue was litterally that the fullscreen check box didn't update the config correctly, which either was always stuck in fullscreen, or wouldn't go into fullscreen. It was fixed a while ago, and this issue should have probably been closed. |
|
Closing fixed and stale issue. |
|
Having this issue too, except neither editing nor deleting that configuration file fixes it. Had to uninstall and delete both directories in |
This issue is not fixed as of 1.9.1 |
Jellyfin Media Player is stuck in full screen after I exited it via ALT+F4 while watching a movie in full screen.
I've tried restarting, uninstalling, manually disabling the
fullscreensetting in the client options, starting a movie and going back to windowed mode that way, F11, ALT+ENTER.This occurred on Windows 10 20H2 with JMP v1.6 using the Windows installer. See my JellyfinMediaPlayer.log.
Solution: Delete
jellyfinmediaplayer.confin%APPDATA%/Local/JellyfinMediaPlayer.Please look into why this happened to prevent future users from having to manually delete the config file. Cheers.
The text was updated successfully, but these errors were encountered: