MCL-18836Launcher Fails to load after new update (linux)
My launcher recently automatically updated upon start. After this update happened, I haven't been able to get the launcher to load. So I went into my files and got out the launcher_log.txt file and examined it a bit.
I found an error message in the txt file, being:
[Error: 2021-07-16 00:19:44.308064404: LauncherPluginLinux.cpp(20)] Failed to load /home/bstrazishar/.minecraft/launcher/liblauncher.so: libsecret-1.so.0: cannot open shared object file: No such file or directory
Reading some other bug reports from earlier this June, I saw other users were experiencing similar issues when the launcher was updated back in June. It's basically the same issue but a little bit different.
So, I have tried uninstalling the launcher and reinstalling multiple times, I have tried updating my linux environment, upgrading all packages, the whole deal. But nothing seems to work.
Is there anything I can do to fix this? If so please help!
I have read all the old bug reports as well, so please submit new information for me. Thank you all and have a wonderful day.
Below I have attached both launcher log files.
Environment
Debian Linux 10
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-post-Debian-1deb10u1)
OpenJDK 64-Bit Server VM (build 11.0.11+9-post-Debian-1deb10u1, mixed mode, sharing)
(Side note, I am simulating a linux virtual machine on my chromebook if that helps anyone solve the issue)
Created Issue:
Launcher Fails to load after new update (linux)
My launcher recently automatically updated upon start. After this update happened, I haven't been able to get the launcher to load. So I went into my files and got out the launcher_log.txt file and examined it a bit.
I found an error message in the txt file, being:
[Error: 2021-07-16 00:19:44.308064404: LauncherPluginLinux.cpp(20)] Failed to load /home/bstrazishar/.minecraft/launcher/liblauncher.so: libsecret-1.so.0: cannot open shared object file: No such file or directory
Reading some other bug reports from earlier this June, I saw other users were experiencing similar issues when the launcher was updated back in June. It's basically the same issue but a little bit different.
So, I have tried uninstalling the launcher and reinstalling multiple times, I have tried updating my linux environment, upgrading all packages, the whole deal. But nothing seems to work.
Is there anything I can do to fix this? If so please help!
I have read all the old bug reports as well, so please submit new information for me. Thank you all and have a wonderful day.
Below I have attached both launcher log files.
Environment
Debian Linux 10
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-post-Debian-1deb10u1)
OpenJDK 64-Bit Server VM (build 11.0.11+9-post-Debian-1deb10u1, mixed mode, sharing)(Side note, I am simulating a linux virtual machine on my chromebook if that helps anyone solve the issue)
Attachments2
![[Mojang] Donuts1000](../../../data/avatars/users/18949.svg){kind=small}
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.