Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-55784

I'm experiencing a "Ticking screen" error when attempting to join a local LAN game.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 1.7.9
    • None
    • Unconfirmed

      This only happens with update 1.7.9. It crashes and gives me this error (see attachment for full report):

      ---- Minecraft Crash Report ----
      // I let you down. Sorry

      Time: 5/24/14 10:26 AM
      Description: Ticking screen

      java.lang.NullPointerException: Ticking screen
      at com.mojang.util.UUIDTypeAdapter.fromUUID(UUIDTypeAdapter.java:22)
      at com.mojang.util.UUIDTypeAdapter.write(UUIDTypeAdapter.java:13)
      at com.mojang.util.UUIDTypeAdapter.write(UUIDTypeAdapter.java:10)
      at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.write(TypeAdapterRuntimeTypeWrapper.java:68)
      at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.write(ReflectiveTypeAdapterFactory.java:89)
      at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.write(ReflectiveTypeAdapterFactory.java:195)
      at com.google.gson.Gson.toJson(Gson.java:593)
      at com.google.gson.Gson.toJson(Gson.java:572)
      at com.google.gson.Gson.toJson(Gson.java:527)
      at com.google.gson.Gson.toJson(Gson.java:507)
      at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:54)
      at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.joinServer(YggdrasilMinecraftSessionService.java:61)
      at bll.a(SourceFile:48)
      at jt.a(SourceFile:41)
      at jt.a(SourceFile:10)
      at ej.a(SourceFile:174)
      at bct.c(SourceFile:78)
      at ban.p(SourceFile:1343)
      at ban.ak(SourceFile:774)
      at ban.f(SourceFile:728)

            Unassigned Unassigned
            NjlsYoshi Nathaniel Seltenright
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: