Uploaded image for project: 'Minecraft Launcher'
  1. Minecraft Launcher
  2. MCL-18847

longjmp-based crash makes it impossible to play minecraft.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 2.2.3554 (Linux)
    • Fix Version/s: None
    • Component/s: Minecraft Launcher
    • Labels:
    • Environment:
      Gentoo Linux, kernel version 5.13.1, KDE Plasma 5.22.3
    • Confirmation Status:
      Unconfirmed

      Description

      After initially encountering the issue in MCL-18836, and installing libsecret, I was able to actually get the launcher to boot up. However, it always crashes with the following error after a few seconds:

      *** longjmp causes uninitialized stack frame ***: terminated
      

      While this always happens occasionally for me, it's 100% consistent now. What's worse is that, because the launcher now asks me to log in every time I boot it up, the time between boot-up and game launch is eaten up by having to type in credentials over and over. I don't know if I'm being asked all the time because the crash keeps it from saving login data properly, or if it's me ignoring the pop-up for the gnome-keyring password thing (in a hurried rush to get to the "play game" button in time).

      I have a coredump of the crash, but I don't know if I'm allowed to upload it (or how to sanitize it to remove any personal information that may be there). At the very least I can share the backtrace when opening it with gdb, though I'm afraid it might not help much:

      #0  0x00007f1430d5351e in raise () at /lib64/libc.so.6
      #1  0x00007f1430d3d536 in abort () at /lib64/libc.so.6
      #2  0x00007f1430d95ad9 in  () at /lib64/libc.so.6
      #3  0x00007f1430e25312 in __fortify_fail () at /lib64/libc.so.6
      #4  0x00007f1430e2522d in  () at /lib64/libc.so.6
      #5  0x00007f1430e2518e in __longjmp_chk () at /lib64/libc.so.6
      #6  0x00007f142ece0fe5 in  () at /usr/lib64/libcurl.so.4
      #7  0x00007f1431b33660 in <signal handler called> () at /lib64/libpthread.so.0
      #8  0x00007f1430e0acff in poll () at /lib64/libc.so.6
      #9  0x00007f1430556e5e in  () at /usr/lib64/libglib-2.0.so.0
      #10 0x00007f1430556f7f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
      #11 0x00007f141a822592 in  ()
      #12 0x000000000291be28 in  ()
      #13 0x00000001aaaaaa00 in  ()
      #14 0x0000006785829a2a in  ()
      #15 0x0000006784e382a6 in  ()
      #16 0x00007ffe78dff108 in  ()
      #17 0x000000000291be20 in  ()
      #18 0x0000000000000001 in  ()
      #19 0x7fffffffffffffff in  ()
      #20 0x00007ffe78dff0c0 in  ()
      #21 0x00007f141a86b5ca in  ()
      #22 0x00000000026fef70 in  ()
      #23 0x00007ffe78dff4e0 in  ()
      #24 0x00007ffe78dff108 in  ()
      #25 0x00007ffe78dff190 in  ()
      #26 0x00007ffe78dff150 in  ()
      #27 0x00007f141a841e6e in  ()
      #28 0x00007f141f8ad928 in  ()
      #29 0x00007ffe78dff100 in  ()
      #30 0x0000000002dbc260 in  ()
      #31 0x00007f141a8b0d4b in  ()
      #32 0x00000000028f7d50 in  ()
      #33 0x0000000002dbc6b0 in  ()
      #34 0x0000000000000000 in  ()
      

      Additionally, if there are any resources on why I'm required to have libsecret installed now, that'd be great. I'm guessing there's a change in how the launcher handles account information, but a link to where I can learn about such changes would be appreciated. Then I could work out if I can avoid using gnome-keyring on my non-gnome desktop, and about any future suddenly-required libraries.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ShimmerFairy Faye N
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: