A small yet quite annoying bug

Whenever Alhena is fullscreened (or just changed from the default resolution), the toolbar positions get all wonky. I would just use it windowed but I would need the text size to be smaller to be comfortable at that size and I can't find a setting to change the text size. Either way, I prefer to use apps fullscreen and this is quite an odd error

/u/Breebee/image/501.png

Posted in: s/Alhena

🐡 Breebee

Jul 28 · 3 months ago

9 Comments ↓

🦎 bluesman [mod] · Jul 28 at 21:54:

@Breebee Interesting. What operating system and how do you change into fullscreen mode? By fullscreen, do you mean the "maximize" button or something else?

If you want to adjust the font size of the app menus, there isn't a setting to do that (yet). If you mean the page fonts, they can be adjusted in the Settings->Font menu.

I'll fix it if I can recreate it.

🐡 Breebee [OP] · Jul 28 at 22:20:

@bluesman I did find where to edit the text size based on your comment so thank you

As for fullscreen, I mean this button. I believe it's technically called the "maximise" button. I'm on arch by the way

— /u/Breebee/image/502.png

🦎 bluesman [mod] · Jul 28 at 22:50:

@Breebee That helps, thanks. Are you running one of the pre-built releases from GitHub or did you build from source? If from source, do you know what version of Java?

I haven't seen that behavior on my Ubuntu or Raspberry Pi desktops. I'll do some research. Are you using Wayland by any chance?

🐡 Breebee [OP] · Jul 28 at 23:52:

@bluesman I am using the pre built from the github (the x64 release) and I am not using wayland (I'm using x11)

🦎 bluesman [mod] · Jul 29 at 00:02:

Perfect. I'll look into it.

🦎 bluesman [mod] · Jul 29 at 04:16:

@Breebee Are you using KDE Plasma on Arch? If so, there's a reported bug with Java 21 related to maximizing windows and popup menus.

I was going to install Arch in VirtualBox for testing but the process was a lot more involved than I anticipated (and I feel that's an understatement).

I'm not totally clear whether the fix has made it into JDK 24 but I might make a one-off install if you'd be willing to test it. If you need something right away, you could grab JDK 24, set the JAVA_HOME variable and use the platform agnostic "Basic" install on GitHub to try it out.

🐡 Breebee [OP] · Jul 29 at 12:38:

@bluesman I am using kde plasma on arch lol. I would be willing to test, yeah. I have jdk 24 installed for other purposes (minecraft modding) so I'll download the platform agnostic version when I get home and see if that does anything

🐡 Breebee [OP] · Jul 29 at 17:16:

@bluesman jdk 24 on the agnostic install works perfectly. It is very likely a java 21 bug.

🦎 bluesman [mod] · Jul 29 at 17:32:

@Breebee Great to hear! I looked through the JDK bug fix lists for 22 through 24 and was worried the fix hadn't been committed.

It's possible they'll backport it but I'll probably start testing 24 anyway. That said, 21 may be the last to support 32-bit operating systems and I want Alhena to work on as many platforms as possible. That doesn't prevent installs based on later versions - I just won't be able to take advantage of new language features in source.

Anyway, thanks for the report and looking into it.


Source