-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Can't escape full screen + menus stay closed (after upgrade to 5.12/5.13) #10731
Comments
@ThiloteE don't you have Linux mint as well? |
I am on an older version of Linux Mint (20.3). I use the flatpak version of JabRef. The newest portable version I can run there is JabRef 5.9, because JabRef requires a newer kernel, which by default is only delivered with Ubuntu 22.0X or something and Linux Mint 20.3 is based on an older Ubuntu. I have not tried any of the deb versions. |
Can you test the latest 5.13 from here? |
I can't reproduce in Ubuntu 22.04, but I don't use Cinnamon |
Can't replicate it in Ubuntu 22.04 using Cinnamon, but I am unable to open JabRef in full-screen, so perhaps not that useful. This might be related to the original part of #4939 ? |
The bug persists. 😢
|
Then this sounds more like a bug in cinnamonn |
I have a similar issue using Linux/i3 wm. Menus close immediately, unless the mouse key is kept pressed. But then, menu options cannot be selected. Menus keyboard shortcuts works fine. Same for 5.13. The issue is not present in 5.11. |
Same issue here; I just installed 5.12 and did not have the issue in 5.11. Updating this because I first thought it had to do with Wayland but maybe not; my other (Xorg?) Ubuntu version was set up differently for displays. From what I can tell it had more to do with using dual displays and which one was set up as primary (the bug only happened when my external display was set up as primary). I installed 5.13 following a link given above and while the bug was still there at first, after a bit more random tests I am back on Wayland + primary external display and all looks well now (no idea why), so I won't touch this anymore - I'll report back if the bug comes back. |
Can you please test this version? https://builds.jabref.org/pull/10808/merge |
The new build works fine on i3, thanks! |
I have the same issue on Ubuntu 22.04.3 with Wayland. The window is in full screen and the menus disappear. I can confirm that installing 5.13 from https://builds.jabref.org/pull/10808/merge solved the issues with the menus for me (they are working normally again), but the window is still in full screen. |
With the build 10808 on i3 there is no problem with switching full-screen on and off. |
I have this problem as well on the latest 5.13 build as of this comment. I can interact with menus by clicking now but the application is still stuck in full screen. Linux Mint 21.2 with Cinnamon 5.8.4. |
I updated to 5.12 today and have a similar issue on Ubuntu 22.04.. In Fullscreen Main Menu is not working. However in window mode, everything works as expected. Update: 5.13 dev solved the issue for me. |
Hi, |
Hi, i have the same Problem on Obuntu 22.04. Sometimes it works to click the windowsbutton + arrowkeys, or just restart RabRef. The Problem only occurs at the first Start of the Software for me. |
Can you try the version with javafx22-ea-28from here? https://builds.jabref.org/jdk-ea/ |
Hi Chris, |
@plyaden |
@calixtus It seems to be about Linux Mint and Cinnamon. - Can you start Cinnamon on arch maybe? |
JabRef 5.13--2024-03-20--047a975 I'm having this same problem (Jabref in fullscreen mode and can't get out of it; clicking menus doesn't open the dropdown). I'm using Linux Mint and Cinnamon. Other programs running at the same time are normal; it's just Jabref. |
I tried this - no improvement. |
JabRef 5.13--2024-03-20--82a0338 The fullscreen-only problem appears only on my laptop (Thinkpad T580) and not on my dual-screen desktop setup. There, the same version of JabRef behaves just fine. I don't know if it's related, but once again JabRef presents the "custom entry types" approval screen on every startup. |
JabRef 5.14--2024-05-07--045f815 If I start JabRef with this command: I append the contents of my jabref.prefs file, which dates from August 2018. |
I had the same problem under Linux Mint 21.3 Cinnamon (6.0.4), kernel 5.15.0-107-generic. I added the line -Dglass.gtk.uiScale=1.01 in the [JavaOptions] section of the JabRef.cfg file. |
This worked for me, but setting JabRef 5.13--2024-04-01--6bdcf63 |
JabRef 5.14--2024-05-29--6a63990 I have no idea if this is relevant, and it probably isn't. However, Linux Mint/Ubuntu today received an update to the X11 window manager and compositor library called mutter, taking it from 7.1 to 8.0. I noticed that one of the changes related to fullscreen maximization and it crossed my mind that there might be something here that intersected with the JabRef fullscreen issue. I have not experienced the fullscreen problem since early May. The changes are described as follows:
The full changelog is here. |
JabRef 5.14-PullRequest11282.236--2024-06-15--49ab67b Still a problem, and now the solution of launching with |
Any updates from the devs (@Siedlerchr, @calixtus) as to what might be causing this? This is still an issue with 5.12, 5.13, and the latest dev build of 5.14. The only reliable solution I have found (which doesn't break fonts) is to regress to 5.10, and that is driving me nuts because renaming files in the cleanup dialog is broken in 5.10 (as per discourse 3999). System info: There's also a very wierd effect I'm noticing, where if the It seems like they're setting some shared variable which persists between sessions, which is not what I would expect, given that the flatpak's behavior should be sandboxed. This is confusing to me. Would erroneous setting of xdg variables in the flatpak be able to do this? |
Hi @Liam-Twomey , thanks for asking. |
Might be some value in the preferences that is reported incorrectly |
The preferences are not the problem, but I think setting the window to full screen instead of just maximizing is causing issues. |
Do you mean setting it to start in fullscreen somewhere in the JabRef preferences? To clarify, none of the users here are reporting that we set it to fullscreen -- it seems like the display is set to something like 1.1x scale, and so the titlebar for the window is outside the screen boundary. I think the menu issues come from the interactable UI elements not being scaled by the same value. Unfortunately, there's no way to force-resize a window in Cinnamon if you can't see the titlebar, so we can't shrink it or manipulate the window at all. I'll keep tabs on this thread, if anyone has testing builds which might fix this, I'd be happy to be a Minty guinea pig. |
I also suspect some interaction involving preferences (and Cinnamon and
javafx), because of I load Jabref with explicit prefs (JabRef -p foobar)
then I have no full screen problem.
Sent from Android phone
…On Fri, Jun 28, 2024, 12:28 AM Christoph ***@***.***> wrote:
Might be some value in the preferences that is reported incorrectly
—
Reply to this email directly, view it on GitHub
<#10731 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF2DBSQBIYYZQZJBUD5OGTZJTYBTAVCNFSM6AAAAABBETJW46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJWGE3TAMRQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In the jabref prefs near the export/import there is a button to view the
current values. Maybe you can check them once it's fine and then afterwards
when it's no longer fine. This would help to verify what values are there
regarding screen size/resolution
Dominik Wujastyk ***@***.***> schrieb am Fr., 28. Juni 2024,
21:56:
… I also suspect some interaction involving preferences (and Cinnamon and
javafx), because of I load Jabref with explicit prefs (JabRef -p foobar)
then I have no full screen problem.
Sent from Android phone
On Fri, Jun 28, 2024, 12:28 AM Christoph ***@***.***> wrote:
> Might be some value in the preferences that is reported incorrectly
>
> —
> Reply to this email directly, view it on GitHub
> <#10731 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAF2DBSQBIYYZQZJBUD5OGTZJTYBTAVCNFSM6AAAAABBETJW46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJWGE3TAMRQGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#10731 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOFZDCSECJ5YTVPRS24BLZJWWW7AVCNFSM6AAAAABBETJW46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGQ3DMMRRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I unfortunately cannot access preferences after the glitch has happened, as I can't open file menus anymore. However, I've done some further testing and found some interesting results.
At this point I suspected that the GNOME fractional scaling used in Cinnamon (and potentially the difference in scales used between my monitors) was messing with the JabRef display scale on monitor 1. I set both monitors' scale to the value used by monitor 2 (which causes no issues) and reinstalled the flatpak. This did not fix the issue. At this point, I thought it was significant that the two versions shared the same remembered window location, and cannot be opened at the same time. All in all, this makes it seem like:
This does raise the possibility of this being a Cinnamon bug rather than a JabRef one. However, I don't see any related bugs on the Cinnamon github, and I doubt JabRef is the only common JavaFX program. If the information I've collected here doesn't provide any clues as to how this might be a javafx bug, I can open a bug report at Cinnamon, it could be an interference between the updated javafx version and Cinnamon. Update: after noticing this cinnamon bug, I also tested limiting display 1 to 60 Hz, but this did not resolve the issue. |
Update: I ran a diff on the 5.13 and 5.10 preference export files. Using the freshly-installed 5.10 as reference for the 5.10 after opening 5.13 once (on the non-breaking monitor) we get the following. Please note that both the lengthy and unchanging
Comparing the
It looks like I resized the 5.10 deb before closing it, but not the 5.13 flatpak, causing only the first diff to talk about the |
JabRef 5.14--2024-06-24--f24a578 Attached below is a diff of the "good" and "bad" prefs. And some useful news: the command
opens a properly-windowed session, while
opens a bad, maximized session with menu misbehaviour. Correction: when I ran I attach the two actual prefs files in case there is some obscure issue connected with the sequence of prefs. |
More experiments. Launching from term with
always gives me a good session. But it's this very same session from which I'm exporting At the present time, in spite of the opposite behaviour I recorded in the previous comment, launching
Is always giving me a good session and using jabref-prefs-bad.xml is always giving me a bad session. All the above testing has beeing going on in a single terminal window. I opened a fresh terminal window and At this point, I can't any more reproduce the bad session generated by |
There's something going on with In prefs-good, changing to But in prefs-bad, changing So this is implicated, but not alone. [more testing] If I go into Preferences and switch on the "memory stick mode" I reliably get a good session, even launching with just except, not any more. Grrrrr. I've spent all evening trying different combinations of good and bad prefs, on or off "memory stick mode" and everything else I can think of. All I can definitely say at present is that |
It might be caused by this commit |
Also the screen size should not me remembered, if it is maximized on close, this causes problems when restarting jabref. |
Can you please check if #11440 solves the problem? The binaries should be available in a couple of minutes. |
JabRef 5.14-PullRequest11440.213--2024-06-30--a76f0a2
Loading with no prefs works first time, but then, after a bad session, never again. |
I tried more debugging at #11440 (comment). Could you retry that? Now after step 4, the window position should be saved, so bad states should not be kept. |
JabRef 5.14-PullRequest11440.219--2024-07-01--6937c6b
|
I have the same problem. |
@wujastyk Do you maybe have the log file at hand? ( Would be interesting what JabRef "thinks". |
Here's the log of starting with just |
Here's the log of starting with |
Here's the log of starting with |
JabRef version
5.12 (latest release)
Operating system
GNU / Linux
Details on version and operating system
Mint 21.2 with Cinnamon 5.8.4
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Appendix
Notice that I'll be able to perform some tests tomorrow if needed, but then I'll just re-install a previous version to be able to work. 😞
Log File
The text was updated successfully, but these errors were encountered: