Unknown error - thread 'main' panicked.

[tazihad]

Everytime I try to sync Google Drive. I get the same error.

thread 'main' panicked at 'internal error: entered unreachable code', celeste/src/launch.rs:2226:33
stack backtrace:

And the app crash.

I get this log from terminal.

❯ flatpak run com.hunterwittenborn.Celeste

(process:2): Gtk-WARNING **: 15:14:27.065: Locale not supported by C library.
        Using the fallback 'C' locale.

(process:15): Gtk-WARNING **: 15:14:27.152: Locale not supported by C library.
        Using the fallback 'C' locale.

(celeste:15): Adwaita-CRITICAL **: 15:14:27.284: ../src/adw-header-bar.c:640: tried to remove non-child 0x564a600437d0 of type 'GtkButton' from 0x564a6003f210 of type 'AdwHeaderBar'

(celeste:15): Adwaita-CRITICAL **: 15:14:27.284: ../src/adw-header-bar.c:640: tried to remove non-child 0x564a6005a300 of type 'GtkButton' from 0x564a6003f3f0 of type 'AdwHeaderBar'
Info: Starting up tray binary...

(process:50): Gtk-WARNING **: 15:14:27.491: Locale not supported by C library.
        Using the fallback 'C' locale.
thread 'main' panicked at 'internal error: entered unreachable code', celeste/src/launch.rs:2226:33
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

(celeste:2): GLib-GIO-WARNING **: 15:14:42.024: Your application does not implement g_application_activate() and has no handlers connected to the 'activate' signal.  It should do one of these.

[hwittenborn]

I just started seeing that error when adding support for Box a few days ago, I didn't know it was happening with other server types though. I'll try to get this reproduced when I get home later today, and let you know when I get home.

In the meantime, you can temporarily fix the issue by deleting ~/.var/app/com.hunterwittenborn.Celeste/config/celeste.db (there might be a directory before config/, I can't remember off the top of my head). I'll send a message here once I have a fix in though.

[hwittenborn]

@tazihad: Can you confirm if the issue is still happening? I haven't been able to find out what triggers the issue yet, and I likewise haven't been able to reproduce it again yet either.

[tazihad]

@hwittenborn I just checked. I get similar error. I have around 1 gb file on google drive. App crash after few minutes during sync. Not sure why.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Exec(SqlxError(Database(SqliteError { code: 787, message: "FOREIGN KEY constraint failed" })))', celeste/src/launch.rs:2281:26

I am using Fedora Kinoite 37. celeste from flathub.

[nboughton]

Host OS: Fedora Silverblue 37 Celeste version: 0.4.1 flatpak Same issue but no stack trace appears in the error window

[hwittenborn]

I'm waiting for the Flatpak to deploy, and then I'm going to give this another look. I'm thinking it might've been fixed since the latest Flatpak release, but I'm not positive yet. The new Flatpak should be out in ~2 hours, but I'll send a message here once it's out.

[hwittenborn]

The Flatpak should be updated now, could you see if the issue persists @tazihad @nboughton?

[tazihad]

@hwittenborn Tried the latest version. Issue still exist.

[nboughton]

Same issue still occurring for me too. I also noted that one of my cpu cores is permanently at 100% whenever Celeste is running.

[ghost]

That's a good find, I'm getting the same issues on my CPU core 15, getting a similar issue on #62

[hwittenborn]

Hmm - it looks like this is only happening for the Google Drive backend - do you guys use any other backends? If not then I'm pretty sure this is related to Google Drive somehow.

[tazihad]

@hwittenborn You are right. I only use Google Drive. Not sure about other cloud service.

[nboughton]

I also only use Google Drive so I can't comment on the other services.

[ghost]

Hmm - it looks like this is only happening for the Google Drive backend - do you guys use any other backends? If not then I'm pretty sure this is related to Google Drive somehow.

I only use Google Drive too, as I get unlimited storage from my institution

[hwittenborn]

Yeah, this is definitely just an issue with Google Drive, I've tried to make other remotes break but I don't recall ever getting anything. I'll see if Google Drive is reporting some kind of information Celeste isn't expecting and send a message once I do some testing.

[ghost]

Yeah, this is definitely just an issue with Google Drive, I've tried to make other remotes break but I don't recall ever getting anything. I'll see if Google Drive is reporting some kind of information Celeste isn't expecting and send a message once I do some testing.

Definitely thanks for being quick to address this issue. Cloud support for my pc is very useful especially for school.

[ghost]

I'll also add releases before v0.4.6 worked fine with syncing, it was just slow

[hwittenborn]

I'll also add releases before v0.4.6 worked fine with syncing, it was just slow

Thanks for the info - I'm still trying to figure out why this is going on, but I'll see if I can find anything that changed in the past few releases that might be causing something.

[ghost]

I'll also add releases before v0.4.6 worked fine with syncing, it was just slow

Thanks for the info - I'm still trying to figure out why this is going on, but I'll see if I can find anything that changed in the past few releases that might be causing something.

I tried downgrading the flatpak, but it gives an error about the database

If it helps my operating system is VanillaOS R8 (Ubuntu Based)

[hwittenborn]

Celeste doesn't currently support downgrading to an earlier version after you update (at least most of the time, whenever the database layout gets updated then you can't go backward).

If you want to go back to an earlier release you'll need to delete rclone.conf and celeste.db in ~/.var/app/com.hunterwittenborn.Celeste/config, and then sign back in to your remotes. You can also do some stuff manually to get it working, but it'd be easiest to just redo everything from scratch.

[ghost]

Celeste doesn't currently support downgrading to an earlier version after you update (at least most of the time, whenever the database layout gets updated then you can't go backward).

If you want to go back to an earlier release you'll need to delete rclone.conf and celeste.db in ~/.var/app/com.hunterwittenborn.Celeste/config, and then sign back in to your remotes. You can also do some stuff manually to get it working, but it'd be easiest to just redo everything from scratch.

Oh okay haha, I'll just wait for this issue to be resolved

[ghost]

This error seems to be persistent even without Wi-Fi or an active Internet. I just wanted to add that.

(celeste:26): Adwaita-CRITICAL **: 01:00:08.705: ../src/adw-header-bar.c:640: tried to remove non-child 0x55e1001f17d0 of type 'GtkButton' from 0x55e1001ea150 of type 'AdwHeaderBar'

(celeste:26): Adwaita-CRITICAL **: 01:00:08.705: ../src/adw-header-bar.c:640: tried to remove non-child 0x55e100201300 of type 'GtkButton' from 0x55e1001ea330 of type 'AdwHeaderBar'
Info: Starting up tray binary...
thread 'main' panicked at 'internal error: entered unreachable code', celeste/src/launch.rs:2310:33
stack backtrace:

[hwittenborn]

Yeah that makes sense @gonzoknows, it's checking previously recorded hashes when that error occurs iirc, so it makes sense that it'd happen like that

[ghost]

Yeah that makes sense @gonzoknows, it's checking previously recorded hashes when that error occurs iirc, so it makes sense that it'd happen like that

Any updates on the status on this Error

[ghost]

Yeah that makes sense @gonzoknows, it's checking previously recorded hashes when that error occurs iirc, so it makes sense that it'd happen like that

New update: I've noticed the thread only panics when there are no more items to sync to google drive.

My example is when I was backing up a Cryptomator vault to google cloud, once it syncs all the files the thread panics then the app basically spits the error and breaks.

[ghost]

Thread panicked in latest release

Running Log

(celeste:20): Adwaita-CRITICAL **: 09:24:36.262: ../src/adw-header-bar.c:640: tried to remove non-child 0x55aba6d047b0 of type 'GtkButton' from 0x55aba6cfc1c0 of type 'AdwHeaderBar'

(celeste:20): Adwaita-CRITICAL **: 09:24:36.263: ../src/adw-header-bar.c:640: tried to remove non-child 0x55aba6d14300 of type 'GtkButton' from 0x55aba6cfc3a0 of type 'AdwHeaderBar'
Info: Starting up tray binary...
thread 'main' panicked at 'internal error: entered unreachable code', celeste/src/launch.rs:2330:33
stack backtrace: