I have this still occurring in 18w31a. I generated a completely new world and noticed "Minecart rolls" appearing in the subtitles when I moved beyond spawn and new chunks were generating.
A zip file of my world save has been attached. (The world was re-created. I tested a few times beforehand to make sure the issue persisted on a new generation, and it does.)
Issue is still present in 17w06a.
I'm getting the same error on a locally hosted server when I try to log in. I'm running Antergos Linux. It began happening after I placed a minecart.
The same developer clarified on a similar bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1287864
The issue is with LWJGL 2.x, and needs to be fixed there (outside of Minecraft or Red Hat.) The LWJGL developers are aware of the issue: https://github.com/LWJGL/lwjgl/issues/118
Whether or not the LWJGL developers fix it in LWJGL 2.x is uncertain given that LWJGL 3.x is in development.
It should also be mentioned, Wayland support is currently not worthwhile until relative/locking pointer confinement is implemented (FPS-style games, including Minecraft, have unusable mouse/pointer control under Wayland because of this.)
Here's a bug report tracking the progress for this on the GNOME Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=744104
Update: the issue seemed to be fixed for me for awhile but then started again randomly and worse than ever. I'm guessing it's a combination of network lag and chunk loading/unloading for the most part but it's not always consistent to be absolutely sure.
Still in 15w47a.
(Update from previously made comments: I'm now fairly convinced this is related to the anti-cheat detection changes made since 15w41a.)
I've done some testing over the past 24+ hours on my server. Normally, the portal issue occurs within the first use or two of a portal and with near 100% reproduction rate. It has occurred every reboot with every snapshot update tried thus far.
I have now set allow-flight to true in server.properties and the issue has not occured since my last reboot (it's been several hours with many people going through portals frequently.) No one thus far has reported any portal bouncing since enabling allow-flight. Whether chunks are loaded or not seems to be irrelevant as both loaded and unloaded areas have seen this resolved since disabling the anti-flight on the server.
I'm guessing the anti-cheat detection is getting false positives of "flight" when portals are used and tries to push people back to their last "good" position and thus causing the portals to bounce people repeatedly.
Can anyone else confirm/deny these results?
Still having the issue in 15w46a.
The issue isn't as bad if the chunks around the portal are loaded, so maybe pre-loading chunks around the portal when it's used could be a solution? Or perhaps increasing the cooldown time for portal usage?
Still happening in 15w45a.
Sometimes it seems fine and potentially fixed, but as time goes on it begins to manifest again more consistently. (Memory leak?)
It's often really bad in Creative Mode, but even in Survival it happens sometimes. And in Survival when it occurs, I often take a point of suffocation damage after being transferred to the Nether/Overworld.
I'm experiencing the same issue. I was fine briefly while in the spawn chunk area, but I teleported away and this same error came up and repeats every time I log back in.
EDIT: After some more testing, I managed to stay logged in briefly in my spawn chunks, but the error occurred immediately whenever I tried to interact with a block/entity (e.g. opening a chest.)
There's a bug report on Red Hat's Bugzilla that identifies the issue as an error with LWJGL parsing xrandr under Wayland and a possible workaround. (link below)
I'm experiencing this on 15w40b. This is most noticeable when using doors.
Confirmed for 1.8.2-pre4.
I was using an alt account to spectate my main account and when I entered the portal to leave the nether, my main went to the overworld as expected, but my spectator account was sent elsewhere in the nether. I even had to log off the server and rejoin to get it to load the chunks for the spectator when this happened.
Issue is still present in 1.8.2-pre4
I've had this happen before. It seems to happen when the game doesn't have enough memory allocated to support the resource packs (e.g. 1GB for a 512x pack.) Allocate more memory to the client and the issue should resolve itself.
Recently noticed this on my small private server (~10 friends play on it.) World was generated with snapshot version 14w11b. Skin issue happens on every time for me on 14w19a after using a portal (nether or ender) or respawning from death. Issue happens in both creative and survival modes. I have not tested Adventure mode, and I'm not sure how I would test this in Spectator mode.
Logging out and back in refreshed the skin correctly. Tested with default resource pack as well as a few custom ones.
Also test on a freshly generated 14w19a single player world with same results. (I just test with 14w20a and the issue still remains.)
I should also note that my friends said my skin looked fine to them, but on my end it was a distorted Steve skin. The same appears to be true the other way around- my friends said their skins were distorted Steve skins but they appeared fine on my end.
In case it matters, I tested this on Windows 7 (.exe game file) with Oracle Java 8 using the latest AMD Catalyst beta driver, and also Ubuntu Linux 14.04 (.jar game file) with Oracle Java 8 and the open-source RadeonSI driver.
My friends confirmed the same thing with Nvidia drivers on Windows 7 (I'm not sure what driver version they used or what Java version.)
Issue still present in 14w19a.
I have to break the fence and wait about 2-3 seconds for the lead to drop.
Recently noticed this on my small private server (~10 friends play on it.) World was generated with snapshot version 14w11b. Skin issue happens on every time for me on 14w19a after using a portal (nether or ender) or respawning from death. Issue happens in both creative and survival modes.
Logging out and back in refreshed the skin correctly. Tested with default resource pack as well as a few custom ones.
Also test on a freshly generated 14w19a single player world with same results.
Moving my comment to https://bugs.mojang.com/browse/MC-54811 as well.
The "minecart rolls" subtitle doesn't seem to occur on world load (at least not consistently.) If you travel outward to where chunks start generating, it appears.