celeste [Bug]: I tried syncing and got this

Bug Description

thread 'main' panicked at src/launch.rs:2489:33: internal error: entered unreachable code stack backtrace: 0: rust_begin_unwind 1: core::panicking::panic_fmt 2: core::panicking::panic 3: celeste::launch::launch::sync_remote_directory 4: celeste::launch::launch::sync_remote_directory::{{closure}} 5: celeste::launch::launch::sync_remote_directory 6: celeste::launch::launch::sync_remote_directory::{{closure}} 7: celeste::launch::launch::sync_remote_directory 8: celeste::launch::launch 9: <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline 10: g_closure_invoke 11: 12: 13: g_signal_emit_valist 14: g_signal_emit 15: 16: g_application_run 17: <O as gio::application::ApplicationExtManual>::run_with_args 18: celeste::main thread 'main' panicked at library/core/src/panicking.rs:221:5: panic in a function that cannot unwind stack backtrace: 0: 0x55a665b84905 - <std::sys::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd7fe9da464dc613a 1: 0x55a665bb35eb - core::fmt::write::h31992ea73d92ffa4 2: 0x55a665b80ecf - std::io::Write::write_fmt::h5015b998fbd1cf65 3: 0x55a665b846de - std::sys::backtrace::print::h5f3f79d7ee85f598 4: 0x55a665b85c29 - std::panicking::default_hook::{{closure}}::hf313047c6f9a0750 5: 0x55a665b859cc - std::panicking::default_hook::hd96acc715f65b6d7 6: 0x55a665b86201 - std::panicking::rust_panic_with_hook::hc3b55609717126a2 7: 0x55a665b86033 - std::panicking::begin_panic_handler::{{closure}}::h6a0db00056d37e77 8: 0x55a665b84dc9 - std::sys::backtrace::__rust_end_short_backtrace::h8bf20a85e9b83f5c 9: 0x55a665b85d44 - rust_begin_unwind 10: 0x55a665bb0565 - core::panicking::panic_nounwind_fmt::hc22db378155c4432 11: 0x55a665bb05f2 - core::panicking::panic_nounwind::he931df6ed8de2736 12: 0x55a665bb0736 - core::panicking::panic_cannot_unwind::h46449aa9b12c6d31 13: 0x55a663cb0f04 - <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline::hbe8669dd5c700595 14: 0x7f9e6c56532f - g_closure_invoke 15: 0x7f9e6c57b2bb - 16: 0x7f9e6c57df83 - 17: 0x7f9e6c5873f9 - g_signal_emit_valist 18: 0x7f9e6c5874c3 - g_signal_emit 19: 0x7f9e6b4f4ee8 - 20: 0x7f9e6b4f5066 - g_application_run 21: 0x55a663b79ec8 - <O as gio::application::ApplicationExtManual>::run_with_args::hf3ae39b800c31d15 22: 0x55a663c210e7 - celeste::main::h478561235040638f 23: 0x55a663d54a63 - std::sys::backtrace::__rust_begin_short_backtrace::h4e646722653f7fdc 24: 0x55a663c54c79 - std::rt::lang_start::{{closure}}::hb1f9c1b6a30502c1 25: 0x55a665b78782 - std::rt::lang_start_internal::h55c3af6c910a5833 26: 0x55a663c24205 - main 27: 0x7f9e6b029d90 - 28: 0x7f9e6b029e40 - __libc_start_main 29: 0x55a663b3b025 - _start 30: 0x0 - thread caused non-unwinding panic. aborting.

Installation Source

Flatpak

What version of Celeste are you using?

v0.8.3

Storage Provider

Google Drive

Mar 17 '25 16:03 Elijah59yf

I also got panic: thread 'main' panicked at src/launch.rs:2515:70: called Option::unwrap() on a None value stack backtrace: thread 'main' panicked at library/core/src/panicking.rs:221:5: panic in a function that cannot unwind stack backtrace: 0: 0x5d8d9c2e1905 - 1: 0x5d8d9c3105eb - 2: 0x5d8d9c2ddecf - 3: 0x5d8d9c2e16de - 4: 0x5d8d9c2e2c29 - 5: 0x5d8d9c2e29cc - 6: 0x5d8d9c2e3201 - 7: 0x5d8d9c2e3033 - 8: 0x5d8d9c2e1dc9 - 9: 0x5d8d9c2e2d44 - 10: 0x5d8d9c30d565 - 11: 0x5d8d9c30d5f2 - 12: 0x5d8d9c30d736 - 13: 0x5d8d9a40df04 - 14: 0x7313b7d0291a - g_closure_invoke 15: 0x7313b7d175c3 - 16: 0x7313b7d19071 - 17: 0x7313b7d1ee01 - g_signal_emit_valist 18: 0x7313b7d1eec3 - g_signal_emit 19: 0x7313b6e8f120 - 20: 0x7313b6e8f2d7 - g_application_run 21: 0x5d8d9a2d6ec8 - 22: 0x5d8d9a37e0e7 - 23: 0x5d8d9a4b1a63 - 24: 0x5d8d9a3b1c79 - 25: 0x5d8d9c2d5782 - 26: 0x5d8d9a381205 - 27: 0x7313b697c188 - 28: 0x7313b697c24b - __libc_start_main 29: 0x5d8d9a298025 - 30: 0x0 - thread caused non-unwinding panic. aborting.

Mar 21 '25 20:03 slowvak

Same, when running Google Drive sync:

thread 'main' panicked at src/launch.rs:2489:33:
internal error: entered unreachable code
stack backtrace:
thread 'main' panicked at library/core/src/panicking.rs:221:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x562b5cb30905 - <unknown>
   1:     0x562b5cb5f5eb - <unknown>
   2:     0x562b5cb2cecf - <unknown>
   3:     0x562b5cb306de - <unknown>
   4:     0x562b5cb31c29 - <unknown>
   5:     0x562b5cb319cc - <unknown>
   6:     0x562b5cb32201 - <unknown>
   7:     0x562b5cb32033 - <unknown>
   8:     0x562b5cb30dc9 - <unknown>
   9:     0x562b5cb31d44 - <unknown>
  10:     0x562b5cb5c565 - <unknown>
  11:     0x562b5cb5c5f2 - <unknown>
  12:     0x562b5cb5c736 - <unknown>
  13:     0x562b5ac5cf04 - <unknown>
  14:     0x7f636da6091a - g_closure_invoke
  15:     0x7f636da755c3 - <unknown>
  16:     0x7f636da77071 - <unknown>
  17:     0x7f636da7ce01 - g_signal_emit_valist
  18:     0x7f636da7cec3 - g_signal_emit
  19:     0x7f636cafe120 - <unknown>
  20:     0x7f636cafe2d7 - g_application_run
  21:     0x562b5ab25ec8 - <unknown>
  22:     0x562b5abcd0e7 - <unknown>
  23:     0x562b5ad00a63 - <unknown>
  24:     0x562b5ac00c79 - <unknown>
  25:     0x562b5cb24782 - <unknown>
  26:     0x562b5abd0205 - <unknown>
  27:     0x7f636c6da188 - <unknown>
  28:     0x7f636c6da24b - __libc_start_main
  29:     0x562b5aae7025 - <unknown>
  30:                0x0 - <unknown>
thread caused non-unwinding panic. aborting.

Mar 22 '25 11:03 lordgreg

I'll join the club. Couldn't copy out of the text area so I'm pasting an OCR from a screenshot, just fyi. Also attempting sync with Google Drive. No idea what's wrong, but I'm uninstalling and probably won't check back.

thread 'main' panicked at src/launch.rs:2489:33:
internal error:
stack backtrace:
thread 'main' panicked at library/core/src/panicking.rs:221:5:
entered unreachable code
panic in a function that cannot unwind Stack backtrace:
OONOAUBWNEF ©
30:
Ox55bf27dea905 O0x55bf27e195eb Ox55bf27de6ecf Ox55bf27dea6de Ox55bf27debc29 Ox55bf27deb9cc Ox55bf27dec201 O0x55bf27dec033 Ox55bf27deadc9 Ox55bf27debd44 0x55bf27e16565 Ox55bf27e165f2 0x55bf27e16736 Ox55bf25T16T04 Ox7fddcedb591la 0x7 fddcedca5c3 Ox7fddcedcc071 0x7 fddceddleO01 0x7 fddceddlec3 0x7 fddcdefel20 0x7 fddcdefe2d7 Ox55bf25ddfec8 Ox55bf25e870e7 Ox55bf25fbaa63 Ox55bf25ebac79 Ox55bf27dde782 Ox55bf25e8a205 Ox7fddcd9eb188 0x7 fddcd9eb24b 0x55bf25dal025
0x0 -
<unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown>
g closure invoke <unknown> <unknown>
g signal emit valist g signal emit <unknown>
g application run <unknown> <unknown> <unknown> <unknown> <unknown> <unknown> <unknown>
__libc start main <unknown> <unknown>
thread caused non-unwinding panic. aborting.

Apr 12 '25 18:04 travisfw

I literally just posted about this, but Celeste apparently can't handle name duplication. In other words, if the same file or directory name is used twice on the same path (no [BLEEP] idea as to why Google would even allow this in the first place!) then it slams the entire sync process into the proverbial brick wall, resulting in a complete app crash.

May 10 '25 00:05 daebreaker