-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work on Ubuntu 23.10.1 #14
Comments
Hi @MechMK1, Then:
|
The output of the command is
The output of
|
Yeah, nothing suspicious there. What apps do you actually try to use in full screen? Chrome works alright for me, try that and see if anything changes. If you have Chrome installed, open it and press F11 to go to full screen. Top panel should show up when you hover your mouse to the top |
I tried it with Chrome, to no avail. I also tried it with Binding of Isaac and other games off Steam, which also didn't work. I wish I could be more helpful, but I don't see any log entries that give any indication what could be wrong. It just doesn't trigger. |
Interesting. I'm not sure games would work, I didn't test that use case. |
An alternative extension Fullscreen Avoider does work with all games I've tested thus far, so I believe that games should work just fine. I'm currently using X11, as is the default for Ubuntu 23.10.1 Note: I've uninstalled Fullscreen Avoider prior to all tests for this extension, just in case you were worried about conflicts |
Alright, I have to admit I haven't tested the extension on X since some time, I'll have a look. Right, disabling other extensions is a key in such cases 🙂 |
Sounds like X may be the source of the trouble then. I was halfway expecting some form of unhandled event being the culprit in this case. |
I checked on X11, it does work. It even works better than on Wayland, panel shows up on top of Firefox, whereas on Wayland that doesn't happen for some reason. |
I've installed the extension and ensured it is enabled. However, when going fullscreen on various applications, the extension does not "activate".
I don't know where relevant log files are located that could help with this issue. I'll add them as directed.
The text was updated successfully, but these errors were encountered: