-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"this is an internal issue with celeste and should be reported" #176
Comments
Hey @donbright, I'm pretty sure the lack of a backtrace is due to some internal logic for how Celeste captures backtraces (I'm not positive, but you're not the first person to have a blank backtrace). Would there be any chance you're using Google Drive to sync your files? That's where I've been seeing this issue in the past. |
Hi, I just tried to sync Google Drive from scratch and I got the same error. Empty stacktrace too. |
I just installed Celeste and setup Google Drive, pCloud and Dropbox. After a while, I also get this unknown error, though in a different place:
|
Just reporting that I've encountered a similar issue when I tried to sync google drive on pop os.
|
First, thanks for you work! I know how to use rclone, but having a nice native GUI always feels better. Just got the same error with Proton, no backtrace:
I was syncing two folders, one of which is ~75MB and 920 files and the other one is 2MB, 5 files. I should say the sync process is pretty slow as first folder was checking for more than 10 hours. Maybe more. And I'm not positive if it finished and on which sync step the error happened. With direct use of rclone the process was way way faster, even with defaults. By default rclone uses 4 threads and it seems Celeste using only one. Would be nice to have ability to set |
@hwittenborn yup, was using Google Drive from linux mint. Thanks. |
Just got this as well. Also Google Drive. |
Update: Instead of running with flatpak, I'm now running with the package from Nixpkgs.
|
Thanks for the information @diogotcorreia! Do you have two files with the same name on your Google Drive in your case then? |
@hwittenborn I have indeed 🙃 |
thread 'main' panicked at src/launch.rs:2406:33:
internal error: entered unreachable code
stack backtrace:
(yes the backtrace was literally blank)
The text was updated successfully, but these errors were encountered: