[GH-ISSUE #32] [BUG] Program freezes after authorising in browser and then won't re-open #10

New Issue

Closed

opened 2026-02-17 17:11:49 -05:00 by yindo · 12 comments

yindo commented 2026-02-17 17:11:49 -05:00

Owner

Copy Link

Copy Source

Originally created by @jontstaz on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/32

The database seems to get corrupted during this process and the program wont open again unless I delete the drop.db file in my ~/.local/share/drop directory. I'm on Arch Linux. I manually compiled the program but the same thing happens with the AppImage as well.. It makes the program unusable. Please help.

Originally created by @jontstaz on GitHub (May 24, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/32 The database seems to get corrupted during this process and the program wont open again unless I delete the `drop.db` file in my `~/.local/share/drop` directory. I'm on Arch Linux. I manually compiled the program but the same thing happens with the AppImage as well.. It makes the program unusable. Please help.

yindo closed this issue 2026-02-17 17:11:49 -05:00

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@DecDuck commented on GitHub (May 24, 2025):

Can you share the log files also present in ~/.local/share/drop?

@DecDuck commented on GitHub (May 24, 2025): Can you share the log files also present in ~/.local/share/drop?

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@jontstaz commented on GitHub (May 25, 2025):

There's only 1 line present:
2025-05-24T20:21:39.032677081+10:00 | INFO | src/lib.rs:180 - detected games missing: │ []

@jontstaz commented on GitHub (May 25, 2025): There's only 1 line present: `2025-05-24T20:21:39.032677081+10:00 | INFO | src/lib.rs:180 - detected games missing: │ []`

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@DecDuck commented on GitHub (May 25, 2025):

Can you try starting it from the terminal with RUST_LOG=debug as an environment variable, and then sending us the logs again?

Can you also provide us with the name & tag of the Docker image you're using, and any logs from the server?

And what branch/tag did you compile yourself, and what AppImage did you download?

Sorry for all the questions :/

@DecDuck commented on GitHub (May 25, 2025): Can you try starting it from the terminal with `RUST_LOG=debug` as an environment variable, and then sending us the logs again? Can you also provide us with the name & tag of the Docker image you're using, and any logs from the server? And what branch/tag did you compile yourself, and what AppImage did you download? Sorry for all the questions :/

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@quexeky commented on GitHub (May 25, 2025):

Aight that makes sense.

We've updated the aur package - could you try installing drop-oss-app (https://aur.archlinux.org/drop-oss-app.git)?

(drop-oss-app-bin hasn't been updated properly)

@quexeky commented on GitHub (May 25, 2025): Aight that makes sense. We've updated the aur package - could you try installing drop-oss-app (https://aur.archlinux.org/drop-oss-app.git)? (drop-oss-app-bin hasn't been updated properly)

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@Pacodastre commented on GitHub (May 25, 2025):

I have the same issue. I can provide some details.

After the app has crashed, I tried to restart it and I got the following error in the terminal:

thread 'main' panicked at /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/droplet-rs-0.7.3/src/ssl.rs:99:6:
called `Result::unwrap()` on an `Err` value: KeyRejected("WrongAlgorithm")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    274905 IOT instruction (core dumped)  ./Drop\ Desktop\ Client_0.3.0-rc-1_amd64.AppImage

I can get the app working again by deleting ~/.local/share/drop and ~/.local/share/drop-app.

I also observed a slightly different behavior. After I authorized the app in the browser, I waited a few minutes without doing anything. I then enter the code provided by the web app into the desktop app, and I got the following error:

The app didn't crash. It let me try a second time, but crashed after inputting the code.

I saw that the Xwayland process is taking up to 40% cpu usage in top while the app is trying to authenticate.

Here is the error logs:

➜  appimage git:(develop) RUST_BACKTRACE=1 RUST_LOG=debug ./Drop\ Desktop\ Client_0.3.0-rc-1_amd64.AppImage
2025-05-25T18:29:37.256513208+01:00 | DEBUG | src/lib.rs:138 - checking if database is set up
2025-05-25T18:29:37.256543082+01:00 | DEBUG | src/database/db.rs:62 - creating data directory at "/home/paco/.local/share/drop"
2025-05-25T18:29:37.256654299+01:00 | DEBUG | src/database/db.rs:77 - Creating database at path /home/paco/.local/share/drop/drop.db
2025-05-25T18:29:37.266513107+01:00 | DEBUG | src/lib.rs:285 - initialized drop client
2025-05-25T18:29:37.311272022+01:00 | DEBUG | src/lib.rs:291 - registered all pre-defined deep links

(drop-app:279610): libayatana-appindicator-WARNING **: 18:29:38.010: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
2025-05-25T18:29:48.517215485+01:00 | DEBUG | src/remote/remote.rs:23 - connecting to url https://drop.havenly.me
2025-05-25T18:29:48.530019848+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/
2025-05-25T18:29:50.276955755+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/
2025-05-25T18:29:50.296562459+01:00 | DEBUG | src/remote/auth.rs:195 - opening web browser to continue authentication
2025-05-25T18:29:50.349559333+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/webbrowser-1.0.4/src/common.rs:61 - background spawn: "/opt/zen-browser-bin/zen-bin" "https://drop.havenly.me/client/54ed2d12-db07-4b3a-be6d-2f3f6ddecc4c/callback"
2025-05-25T18:30:06.264911370+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/
2025-05-25T18:30:06.322605627+01:00 | DEBUG | src/remote/auth.rs:112 - handshake responsded with 200

thread 'main' panicked at /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/droplet-rs-0.7.3/src/ssl.rs:99:6:
called `Result::unwrap()` on an `Err` value: KeyRejected("WrongAlgorithm")
stack backtrace:
   0: __rustc::rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: drop_app_lib::remote::auth::generate_authorization_header
4: drop_app_lib::remote::auth::recieve_handshake
   5: drop_app_lib::remote::commands::manual_recieve_handshake
   6: drop_app_lib::run::{{closure}}
   7: tauri::webview::Webview<R>::on_message
   8: tauri::ipc::protocol::get::{{closure}}
   9: tauri::manager::webview::WebviewManager<R>::prepare_pending_webview::{{closure}}
  10: tauri_runtime_wry::create_webview::{{closure}}
  11: webkit2gtk::auto::web_context::WebContextExt::register_uri_scheme::callback_func
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: g_main_context_iteration
  26: gtk_main_iteration_do
  27: tao::platform_impl::platform::event_loop::EventLoop<T>::run_return
  28: drop_app_lib::run
  29: drop_app::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[1]    279610 IOT instruction (core dumped)  RUST_BACKTRACE=1 RUST_LOG=debug

Let me know if you want a full rust backtrace.

@Pacodastre commented on GitHub (May 25, 2025): I have the same issue. I can provide some details. After the app has crashed, I tried to restart it and I got the following error in the terminal: ``` thread 'main' panicked at /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/droplet-rs-0.7.3/src/ssl.rs:99:6: called `Result::unwrap()` on an `Err` value: KeyRejected("WrongAlgorithm") note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [1] 274905 IOT instruction (core dumped) ./Drop\ Desktop\ Client_0.3.0-rc-1_amd64.AppImage ``` I can get the app working again by deleting `~/.local/share/drop` and `~/.local/share/drop-app`. I also observed a slightly different behavior. After I authorized the app in the browser, I waited a few minutes without doing anything. I then enter the code provided by the web app into the desktop app, and I got the following error:  The app didn't crash. It let me try a second time, but crashed after inputting the code. I saw that the Xwayland process is taking up to 40% cpu usage in top while the app is trying to authenticate. Here is the error logs: ``` ➜ appimage git:(develop) RUST_BACKTRACE=1 RUST_LOG=debug ./Drop\ Desktop\ Client_0.3.0-rc-1_amd64.AppImage 2025-05-25T18:29:37.256513208+01:00 | DEBUG | src/lib.rs:138 - checking if database is set up 2025-05-25T18:29:37.256543082+01:00 | DEBUG | src/database/db.rs:62 - creating data directory at "/home/paco/.local/share/drop" 2025-05-25T18:29:37.256654299+01:00 | DEBUG | src/database/db.rs:77 - Creating database at path /home/paco/.local/share/drop/drop.db 2025-05-25T18:29:37.266513107+01:00 | DEBUG | src/lib.rs:285 - initialized drop client 2025-05-25T18:29:37.311272022+01:00 | DEBUG | src/lib.rs:291 - registered all pre-defined deep links (drop-app:279610): libayatana-appindicator-WARNING **: 18:29:38.010: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. 2025-05-25T18:29:48.517215485+01:00 | DEBUG | src/remote/remote.rs:23 - connecting to url https://drop.havenly.me 2025-05-25T18:29:48.530019848+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/ 2025-05-25T18:29:50.276955755+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/ 2025-05-25T18:29:50.296562459+01:00 | DEBUG | src/remote/auth.rs:195 - opening web browser to continue authentication 2025-05-25T18:29:50.349559333+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/webbrowser-1.0.4/src/common.rs:61 - background spawn: "/opt/zen-browser-bin/zen-bin" "https://drop.havenly.me/client/54ed2d12-db07-4b3a-be6d-2f3f6ddecc4c/callback" 2025-05-25T18:30:06.264911370+01:00 | DEBUG | /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.15/src/connect.rs:625 - starting new connection: https://drop.havenly.me/ 2025-05-25T18:30:06.322605627+01:00 | DEBUG | src/remote/auth.rs:112 - handshake responsded with 200 thread 'main' panicked at /home/paco/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/droplet-rs-0.7.3/src/ssl.rs:99:6: called `Result::unwrap()` on an `Err` value: KeyRejected("WrongAlgorithm") stack backtrace: 0: __rustc::rust_begin_unwind 1: core::panicking::panic_fmt 2: core::result::unwrap_failed 3: drop_app_lib::remote::auth::generate_authorization_header 4: drop_app_lib::remote::auth::recieve_handshake 5: drop_app_lib::remote::commands::manual_recieve_handshake 6: drop_app_lib::run::{{closure}} 7: tauri::webview::Webview<R>::on_message 8: tauri::ipc::protocol::get::{{closure}} 9: tauri::manager::webview::WebviewManager<R>::prepare_pending_webview::{{closure}} 10: tauri_runtime_wry::create_webview::{{closure}} 11: webkit2gtk::auto::web_context::WebContextExt::register_uri_scheme::callback_func 12: <unknown> 13: <unknown> 14: <unknown> 15: <unknown> 16: <unknown> 17: <unknown> 18: <unknown> 19: <unknown> 20: <unknown> 21: <unknown> 22: <unknown> 23: <unknown> 24: <unknown> 25: g_main_context_iteration 26: gtk_main_iteration_do 27: tao::platform_impl::platform::event_loop::EventLoop<T>::run_return 28: drop_app_lib::run 29: drop_app::main note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. [1] 279610 IOT instruction (core dumped) RUST_BACKTRACE=1 RUST_LOG=debug ``` Let me know if you want a full rust backtrace.

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@DecDuck commented on GitHub (May 25, 2025):

Thanks.

Could you check the image tag for the server and client version?

@DecDuck commented on GitHub (May 25, 2025): Thanks. Could you check the image tag for the server and client version?

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@Pacodastre commented on GitHub (May 25, 2025):

I use the following:
server: decduck/drop-oss:v0.2.0-beta (docker image)
client: Drop Desktop Client_0.3.0-rc-1_amd64.AppImage (generated from source)

@Pacodastre commented on GitHub (May 25, 2025): I use the following: server: `decduck/drop-oss:v0.2.0-beta` (docker image) client: `Drop Desktop Client_0.3.0-rc-1_amd64.AppImage` (generated from source)

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@quexeky commented on GitHub (May 25, 2025):

That's going to be it is my guess - the v0.2.0 and v0.3.0 client and server are incompatible. Could you try with the drop desktop client 0.2.0 or 0.2.1?

Either that or upgrate the server to nightly

@quexeky commented on GitHub (May 25, 2025): That's going to be it is my guess - the v0.2.0 and v0.3.0 client and server are incompatible. Could you try with the drop desktop client 0.2.0 or 0.2.1? Either that or upgrate the server to nightly

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@DecDuck commented on GitHub (May 25, 2025):

To upgrade to nightly, you can checkout the docs here: https://docs.droposs.org/docs/next/guides/quickstart

@DecDuck commented on GitHub (May 25, 2025): To upgrade to nightly, you can checkout the docs here: https://docs.droposs.org/docs/next/guides/quickstart

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@jontstaz commented on GitHub (May 26, 2025):

Well, I updated to the nightly image for the server and I have the latest binary (tried both the AUR packages + the latest 0.2.1 AppImage from this repo but am getting the same issue on all of the above..

2025-05-27T08:29:34.441988609+10:00 | WARN | src/remote/auth.rs:81 - DropServerError { status_code: 403, status_message: "Invalid nonce signature.", message: "Invalid nonce signature.", url: "https://<redacted>/api/v1/client/user?" }
2025-05-27T08:29:34.443841208+10:00 | WARN | src/remote/auth.rs:147 - error with authentication: server returned an invalid response: 403 Invalid nonce signature.

And the application displays the following message:

Also, the server logs spit out the following 4 lines each time this happens:

drop-1      | [Vue Router warn]: No match found for location with path "/community"
drop-1      | [Vue Router warn]: No match found for location with path "/docs/access/content"
drop-1      | [Vue Router warn]: No match found for location with path "/docs/access/network"
drop-1      | [Vue Router warn]: No match found for location with path "/docs/access/account"

@jontstaz commented on GitHub (May 26, 2025): Well, I updated to the nightly image for the server and I have the latest binary (tried both the AUR packages + the latest 0.2.1 AppImage from this repo but am getting the same issue on all of the above.. ``` 2025-05-27T08:29:34.441988609+10:00 | WARN | src/remote/auth.rs:81 - DropServerError { status_code: 403, status_message: "Invalid nonce signature.", message: "Invalid nonce signature.", url: "https://<redacted>/api/v1/client/user?" } 2025-05-27T08:29:34.443841208+10:00 | WARN | src/remote/auth.rs:147 - error with authentication: server returned an invalid response: 403 Invalid nonce signature. ``` And the application displays the following message:  Also, the server logs spit out the following 4 lines each time this happens: ``` drop-1 | [Vue Router warn]: No match found for location with path "/community" drop-1 | [Vue Router warn]: No match found for location with path "/docs/access/content" drop-1 | [Vue Router warn]: No match found for location with path "/docs/access/network" drop-1 | [Vue Router warn]: No match found for location with path "/docs/access/account" ```

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@quexeky commented on GitHub (May 26, 2025):

The [Vue Router warn] issues are expected - we haven't implemented pages for them.

Your version still don't match. You either need nightly and the client generated from source, or the v0.2.0-beta tag and the downloaded client (0.2.0). We don't have a v0.3.0 AUR package for the client yet, which is the only version compatible with the current nightly server.

@quexeky commented on GitHub (May 26, 2025): The [Vue Router warn] issues are expected - we haven't implemented pages for them. Your version still don't match. You either need nightly and the client generated from source, or the v0.2.0-beta tag and the downloaded client (0.2.0). We don't have a v0.3.0 AUR package for the client yet, which is the only version compatible with the current nightly server.

yindo commented 2026-02-17 17:11:50 -05:00

Author

Owner

Copy Link

Copy Source

@Pacodastre commented on GitHub (May 26, 2025):

That's going to be it is my guess - the v0.2.0 and v0.3.0 client and server are incompatible. Could you try with the drop desktop client 0.2.0 or 0.2.1?

Either that or upgrate the server to nightly

Downgrading the client fixed the issue. Thanks!

@Pacodastre commented on GitHub (May 26, 2025): > That's going to be it is my guess - the v0.2.0 and v0.3.0 client and server are incompatible. Could you try with the drop desktop client 0.2.0 or 0.2.1? > > Either that or upgrate the server to nightly Downgrading the client fixed the issue. Thanks!

yindo referenced this issue 2026-02-17 17:12:06 -05:00

[PR #10] [MERGED] Library UI update #103

yindo changed title from [BUG] Program freezes after authorising in browser and then won't re-open to [GH-ISSUE #32] [BUG] Program freezes after authorising in browser and then won't re-open 2026-06-05 14:24:19 -04:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

develop

depot-fixing

store

small-fixes

v4

160-generic-library-providers

bigpicturemode

113-bug-libayatana-is-a-lazy-dependency-instead-of-a-linked-one

importexport

fix-cmd-window

AdenMGB-small-feats

136-native_model-not-updating-versions

main

52-feature-request-add-this-page-is-intentionally-left-blank-page-on-missing-pages

102-feature-request-ability-to-use-drop-client-without-being-logged-in

beeth-appimage-fixes

async

55-feature-request-game-scanning-for-dropdata-to-import-existing-games

49-bug-broken-auto-release-for-ubuntu-24-and-ubuntu-24-arm

42-feature-request-url-downloader

46-bug-community-news-tabs-sign-you-out

38-cloud-save-implementation

cloud-saves

gamepads

v0.4.0-rc-4

v0.4.0-rc-3

v0.4.0-rc-2

v0.4.0-rc-1

v0.4.0

v0.3.5-torrential-alpha

v0.3.4

v0.3.3

v0.3.2

v0.3.2-dl

v0.3.1-appimage

v0.3.1-mac

v0.3.1

v0.3.0

v0.3.0-rc-8

v0.3.0-rc-7

v0.3.0-rc-6

v0.3.0-rc-5

v0.3.0-rc-4

v0.3.0-rc-3

v0.3.0-rc-2

dev-v0.2.1-beta

dev-v0.3.0-rc-1

app-v0.2.0-beta

v0.2.0-beta

v0.2.0-beta-prerelease-1

v0.1.0-beta

Labels

Clear labels

bug

confirmed

duplicate

feature

needs-triage

pull-request

Mirrored from GitHub Pull Request

support

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

yindo

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Drop-OSS/drop-app#10