Please reread, this is not a duplicate. The linked issue is about the game freezing, this issue is about a button that doesn't work. The game is still responsive apart from the dialog that steals focus.
They are similar but different issues affecting the same part of the game.
Toggling between showing/hiding the ui brings the fps above 200 again. I don't know what could be causing it. Is there any GPU debugging to show what's on screen that could be causing it?
However, going into a single player world the fps is above 200.
Few hours later, issue appeared again. I'm sitting around ~30 fps with GPU usage at 8%.
Some servers have mixed survival/creative mechanics, and barriers should not be obtained. Being breakable isn't part of the issue. Being obtainable without /give is.
For reference if anyone else encounters this error, it is fixable by adding -Dswing.systemlaf=javax.swing.plaf.metal.MetalLookAndFeel to the commandline between java and -jar
Example:
java -Dswing.systemlaf=javax.swing.plaf.metal.MetalLookAndFeel -jar Minecraft.jar
As a temporary solution, I changed my shortcut to run "rm ~/.minecraft/launcher.jar ~/.minecraft/launcher.pack.lzma; java -jar /home/michael/Downloads/Minecraft.jar"
Yes, the crash still occurs on 1.8.
$ java -jar Minecraft.jar
Bootstrap (v5)
Current time is Nov 11, 2014 2:57:00 PM
System.getProperty('os.name') == 'Linux'
System.getProperty('os.version') == '3.13.0-24-generic'
System.getProperty('os.arch') == 'amd64'
System.getProperty('java.version') == '1.8.0_25'
System.getProperty('java.vendor') == 'Oracle Corporation'
System.getProperty('sun.arch.data.model') == '64'
Looking for update
Downloading: https://s3.amazonaws.com/Minecraft.Download/launcher/launcher.pack.lzma
Got reply in: 371ms
No update found.
Reversing LZMA on /home/michael/.minecraft/launcher.pack.lzma to /home/michael/.minecraft/launcher.pack
Unpacking /home/michael/.minecraft/launcher.pack to /home/michael/.minecraft/launcher.jar
Cleaning up /home/michael/.minecraft/launcher.pack
Starting launcher.
[14:57:05 INFO]: Minecraft Launcher 1.5.3 (through bootstrap 5) started on linux...
[14:57:05 INFO]: Current time is Nov 11, 2014 2:57:05 PM
[14:57:05 INFO]: System.getProperty('os.name') == 'Linux'
[14:57:05 INFO]: System.getProperty('os.version') == '3.13.0-24-generic'
[14:57:05 INFO]: System.getProperty('os.arch') == 'amd64'
[14:57:05 INFO]: System.getProperty('java.version') == '1.8.0_25'
[14:57:05 INFO]: System.getProperty('java.vendor') == 'Oracle Corporation'
[14:57:05 INFO]: System.getProperty('sun.arch.data.model') == '64'
[14:57:05 INFO]: JFX is already initialized
The program 'java' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 593 error_code 143 request_code 139 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
If I update the timestamp on launcher.jar (make a backup, and copy from backup each time), the launcher works correctly.
Note that because I hit 3GB yesterday, my internet is incredibly slow, and I now cannot download the files.
It shouldn't make any difference. I'm about to go to bed, but I'll try in morning
The video can be viewed at http://youtu.be/sIDhLISWGkw
It doesn't result in a crash report.
If you like, I can try to take a video.
They have different error messages, with different hardware configurations.
How are they duplicates?
Update: It also crashes using Oracle Java
I recreated the world in vanilla and made the last screenshot.
Seed: 1854626679306623117
Coords added in screenshot
Note that the world generates with dirt there, and the grass then spreads, so you may need to wait a while.
Reinstalling the application fixed the issue.
This does not occur with Oracle Java, it's an issue of the Openjdk java. Also this issue is still marked duplicate despite not being a duplicate. At least not of the issue it's marked a duplicate of.