Adamcake
Chromium Profile error preventing flatpak launch (Bazzite stable and GNOME 49)
Getting off and on issues with Bolt launcher after recent updates, I have to fully delete the launcher to get it to launch. I can fix it by clearing out the entire set of config files as a workaround, but the flatpak is outputting the following when run in terminal, I replaced my hostname as "[[my hostname]]":
flatpak run com.adamcake.Bolt [2:2:1104/182749.669938:ERROR:chrome/browser/process_singleton_posix.cc:358] The profile appears to be in use by another Chromium process (2) on another computer ([[my hostname]]). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium. [2:2:1104/182749.669988:ERROR:chrome/browser/ui/views/message_box_dialog.cc:198] Unable to show message box: Chromium - The profile appears to be in use by another Chromium process (2) on another computer ([[my hostname]]). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium. [2:2:1104/182749.670100:ERROR:cef/libcef/browser/main_runner.cc:77] ContentMainRun failed with exit code 21 Exiting with error: CefInitialize exit_code 0 terminate called without an active exception Received signal 6 #0 0x7f7f866b0922 (/app/opt/bolt-launcher/libcef.so+0x96b0921) #1 0x7f7f8669f49e (/app/opt/bolt-launcher/libcef.so+0x969f49d) #2 0x7f7f866b0398 (/app/opt/bolt-launcher/libcef.so+0x96b0397) #3 0x7f7f7c8425c0 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x415bf) #4 0x7f7f7c89b344 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x9a343) #5 0x7f7f7c84250e gsignal #6 0x7f7f7c829882 abort #7 0x7f7f7caadf7d (/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33+0xadf7c) #8 0x7f7f7cac35da (/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33+0xc35d9) #9 0x7f7f7caad9dd std::terminate() #10 0x559f387acee1 (/app/opt/bolt-launcher/bolt+0x71ee0) #11 0x559f38798341 (/app/opt/bolt-launcher/bolt+0x5d340) #12 0x559f3879823f (/app/opt/bolt-launcher/bolt+0x5d23e) #13 0x7f7f7c82b3c8 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x2a3c7) #14 0x7f7f7c82b48b __libc_start_main #15 0x559f3877a955 (/app/opt/bolt-launcher/bolt+0x3f954) r8: 0000000000000000 r9: 0000000000000400 r10: 0000000000000008 r11: 0000000000000246 r12: 00007f7f7adc0f40 r13: 0000000000000000 r14: 0000000000000006 r15: 0000000000000000 di: 0000000000000002 si: 0000000000000002 bp: 00007ffd9dc36690 bx: 0000000000000002 dx: 0000000000000006 ax: 0000000000000000 cx: 00007f7f7c89b344 sp: 00007ffd9dc36650 ip: 00007f7f7c89b344 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace]
If any more information would be helpful I'm glad to give it.
To be clear I can search for "SingletonLock" and delete the ones under com.adamcake.bolt, so there is a workaround, but an automated solution for this would be nice.
This is the same as #132, but I'm surprised that it's only started happening after recent updates, I was actually hoping it would be fixed by the update to Chromium 139.
