From ArchWiki
Jump to: navigation, search

One more way to fix window manager related issues

Faced some sort of "rendering problem" on MATE few days ago. Wmname crashed MATE completely, but I found a nice fix on one of Linux Mint forums.

Here is git repo with description and sources. It's a simple jar that injects into Java X11 class and force it to return fixed, user defined string, instead of actual WM name.

Already posted PKGBUILD to AUR and think about posting this solution here. Is there anything special I should know/do before posting?

Ffuugoo (talk) 10:06, 25 May 2014 (UTC)

Thanks for this info. It is about MATE so you should add it to MATE page.
If there is any bug link about this, please add it too so after this is fixed. Such workaround could/should be removed.
--Fengchao (talk) 07:08, 14 June 2014 (UTC)
The trick here that it is not just about MATE, but another solution to Java#Impersonate another window manager.
And as it's more accurate way (than wmname) to solve this problem, I think it should be marked as recomended.
--Ffuugoo (talk) 09:32, 30 June 2014 (UTC)
Then it is ok to add it here. Any information about the bug in upstream? If there is, please add it here for tracking.--Fengchao (talk) 09:02, 27 July 2014 (UTC)

Use of Template:App

Woud that really look any better from this? --Dettalk 15:21, 9 September 2017 (UTC)

The descriptions in those tables are useless, they don't convey new information over the package name and repeat the header name with every entry. Java#Unsupported_JVMs below has even more header bloat: except for Java#32-bit Java SE all contain but a single sentence. The "unsupported" is implied anyway, either from the AUR or from the description.
Finally, I'm aware you don't care much for convention but every other article in the wiki uses Template:App to summarize different packages. -- Alad (talk) 17:26, 9 September 2017 (UTC)
I'm not sure why you're aware I don't care much for convention, but why am I starting a talk page section on an issue I don't care about? As far as I can see, Firefox#Installing includes homepage links on each. In Java#Installation each of those would pretty much share the same one and still include some kind of a description. --Dettalk 17:36, 9 September 2017 (UTC)
Fraction of the size: User:Alad/Java. There's no point in all these descriptions about versioning when it's all included in the package description. e.g. jdk6AUR: "Oracle Java 6 Development Kit (public release - end of support)" -- Alad (talk) 17:58, 9 September 2017 (UTC)
Well, that looks very different. Let's do it? --Dettalk 18:01, 9 September 2017 (UTC)
[1] -- Alad (talk) 19:09, 9 September 2017 (UTC)

GTK+3 on Java 9

Java 9 released on the 21/9/2017, and with it came the ability to force AWT, Swing and JavaFX programs to use GTK+3[2] with the GTK Look and Feel. As such I propose editing the GTK Look and Feel section [3] to include this. GTK+3 is enabled using -Djdk.gtk.version=3 (or 2, 2.2) in _JAVA_OPTIONS, meaning it can be placed in a users .rc file or in /etc/environment.

Note that to enable this, users will have to use extra/jdk9-openjdk, extra/jre9-openjdk and extra/jre9-openjdk-headless, before changing their version using archlinux-java.