Björn
Assigned
Reported
MC-175233
MC sends a legacy resize request instead of a fullscreen request to the window manager
Community Consensus
MCPE-64167
Friend can't join anyone
Duplicate
MC-160724
Slimes play player footstep sounds underneath their squishy sounds
Cannot Reproduce
MC-141446
Crash in newly created world
Invalid
MC-132470
Initializing game: java.lang.ExceptionInInitializerError while initializing LWJGL
Works As Intended
MC-129216
Crash: Couldn't render entity
Invalid
MC-126508
Crash: Exception in thread "main" java.lang.UnsatisfiedLinkError: Failed to dynamically load library
Fixed
MCPE-30486
Chat doesnt work between two players
Cannot Reproduce
MCPE-30197
No mending books from fishing
Won't Fix
MCPE-26044
Windows 10 edition crash on startup
Duplicate
MC-24547
Mac OS X command key gets stuck
Duplicate
MC-22033
Multi button mouse unusable on Mac OS X
Incomplete
MC-19132
Query/Connect using SRV record not working anymore
Cannot Reproduce
Comments
This still happens in 1.16.4. Have to regularly break ladders to free villagers stuck trying to get past trapdoors.
In my experience villagers are getting stuck in wells even after I raise the water level, something about their AI is messing up when they are in those wells. The only way I have found to avoid this is by first raising the water level by 1, then breaking one block of the well to make flowing water, and finally placing another solid block right in front of the hole to prevent the water from flowing too far. This makes the villagers get pulled out of the well.
Yes, I tried launching pre9 and it crashed immediately.
I don't even see the Mojang screen. Minecraft doesn't startup at all, it crashes immediately on launch.
The issue is not fixed at all. Didn't see my edit?
Looks like it's still an LWJGL issue.
Ah. And that is not the same as "Confirmed"?
I am afraid you don't know what a bug is, then. This is a game crash; a crash is a bug.
Question. What does "Community consensus" mean?
Tried updating Java and running 18w11a using JDK 1.8.0_161, didn't work.
Now i investigated more.
This happend after we typed a lot of "swear"words. There are multiple words in swedish that is considered as a swearword in english.
We tried a few, and after that ONLY my friend can see what i write.
This is the status right now:
My friend can ONLY see what i type in the realm. Noone else can se what anyone else is typing.
I checked the settings in xbox, and my friend wasnt muted.
Same here. This must be a new bug from one of the latest updates.
I can confirm this is still an issue in 1.8.2 pre-releases, seeing terrain borders at half-generated lakes where 1.7 chunks meets 1.8 ones. Perhaps affected versions should be extended to 1.8.2-pre1 to 1.8.2-pre4 and the environment updated to Java 8u25.
Replacing the LWJGL libs didn't work for me.
Thanks for the hint. It's still a concern, versions updated.
Hmm... I did some more digging into how SRV records work. It really seems to be my own fault at the end! Ticket can stay closed and I apologize for the confusion 😉
Just as a little explain what happened:
Setting up and using an SRV record indeed tells the client to use the real address behind the record. Blocking this would result in the described error.
What I mixed up here was the need to block this "internal" port. This is NOT needed when you're not using a proxy (which is doing the authentication, while the server itself then would need to run in offline mode).
Regards
DerFlash
Interesting, you're right (but not completely g).
I think you've found some hint for the issue itself here.
You're right with the fact that the server is (actually) working. It seems to be because I've removed the iptables rule preventing access to the port directly from outside. This is to prevent people from even knowing that the server is running on this port. So they just know that its running at vanilla.cube-nation.de. This worked fine with all versions for now and is how SRV records should be used.
But somehow the 1.6 seems to use the redirection address for further communication instead of still the SRV record, so the connection will timeout/disconnect as soon as the iptables rule for direct access is in place.
So to sum it up:
if you've access to both (vanilla.cube-nation.de + cube-nation.de:22296) it works although the client should never use later address since I've given him the first one
if you're blocking the direct access to cube-nation.de:22296, the SRV record vanilla.cube-nation.de pointing to this address stops working
PS: As you may notice, the iptables rule is in place again. Feel free to check again - server should not "really" respond anymore.
Hope that may help to find the exact problem here.
dublicates https://mojang.atlassian.net/browse/MC-1580
Having the same issue with a long-time world I started with 1.7. Load time in 1.16.5 was fairly modest but when I updated to 1.17 it shot up probably a good 3x - 4x.
I also see those same errors in the log file. Though even if I load the world in an area where those errors don't show up the load time is still very slow. I'm tempted to try 1.17-pre2 and see if that is faster.