infinite loading

[heyalbero]

I tried to install version 0.1, but ''TypeError: Failed to fetch'' was showing, I downloaded 0.2.1, because I read another issue here, and now it has an infinite loading

[theCapypara]

Can you try reloading the plugin? This is a known issue that happens sometimes, I tried some things to fix it but haven't really found the cause yet.

[heyalbero]

I try reloading and reinstall

Decky-Recorder_2024-04-26_15-16-00.mp4

[ThePerfectVale]

Hi! Same issue here. Reloading gives me this error:
"TypeError: plugin_exports.default is not a function"
"at PluginLoader.importReactPlugin (http://localhost:1337/frontend/chunk-BpFm7XFv.js:7067:56)"
"at async PluginLoader.importPlugin (http://localhost:1337/frontend/chunk-BpFm7XFv.js:7044:13)"

Reinstalling seems to fix the issue temporarily until I reboot. It is also unable to detect my Syncthing GTK, so I had to choose Syncthing.

I am on SteamOS 3.6.8, with Decky version v3.0.0-pre4. The plugin's version is 0.2.1-389a842.

[DoronLGN]

I'm having a similar issue with the test version, whose use was prompted by the issue with the stable version heyalbero had.

[theCapypara]

The plugin currently is only tested and supported on stable Decky and SteamOS.

[Spencer-0003]

Getting the same issue with Decky v2.12.3, SteamOS 3.5.19 and plugin version 0.2.1-389a842 also using Syncthing GTK.

[agentwolf88]

Still no fix?

[BryanJacobs]

For me on Bazzite, the infinite loading happens after every boot. But reloading the plugin once from Decky's settings always fixes it.

[theCapypara]

@BryanJacobs Are you using Decky Loader 3?

[BryanJacobs]

@BryanJacobs Are you using Decky Loader 3?

v3.0.0, yes.

[theCapypara]

Then I guess this issue is still not resolved. As I said before I have no idea what causes this and would need help to fix it.

[agentwolf88]

With Holoiso and ChimeraOS it works fine but not with Bazzite. :( I need Bazzite!

[agentwolf88]

Is there a log file where we can see what happens?

[fsworld009]

You can find logs for plugins in ~/homebrew/logs/{plugin-id}, for this plugin they are in ~/homebrew/logs/decky-syncthing/

I'm seeing the same issue on Bazzite with decky loader v3.0.2-pre2, logs below:

watchlog.log

2024-10-15T15:01:12.441007868+08:00 INFO::started 0.2.0.
2024-10-15T15:01:12.455412456+08:00 ERROR::panicked: called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "Failed to run systemctl command ('daemon-reload'): exit status: 1. Stderr: Failed to connect to bus: No such file or directory\n" }

last_panic.txt

called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "Failed to run systemctl command ('daemon-reload'): exit status: 1. Stderr: Failed to connect to bus: No such file or directory\n" }
   0: decky_syncthing_watchdog::panic_util::register_panic_hook::{{closure}}
   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/alloc/src/boxed.rs:2029:9
      std::panicking::rust_panic_with_hook
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:783:13
   2: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:657:13
   3: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:171:18
   4: rust_begin_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
   5: core::panicking::panic_fmt
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:72:14
   6: core::result::unwrap_failed
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/result.rs:1649:5
   7: decky_syncthing_watchdog::main::{{closure}}
   8: tokio::runtime::scheduler::current_thread::Context::enter
   9: tokio::runtime::context::set_scheduler
  10: tokio::runtime::runtime::Runtime::block_on
  11: decky_syncthing_watchdog::main
  12: std::sys_common::backtrace::__rust_begin_short_backtrace
  13: std::rt::lang_start::{{closure}}
  14: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/ops/function.rs:284:13
      std::panicking::try::do_call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552:40
      std::panicking::try
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516:19
      std::panic::catch_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142:14
      std::rt::lang_start_internal::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148:48
      std::panicking::try::do_call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552:40
      std::panicking::try
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516:19
      std::panic::catch_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142:14
      std::rt::lang_start_internal
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148:20
  15: main
  16: __libc_start_call_main
  17: __libc_start_main_alias_1
  18: _start

Hope this helps.

Current workaround is to reload the plugin manually in decky loader menu, as previous post pointed out.

[theCapypara]

Hm, I'm not sure how to solve this. This is either a bug in Decky Loader or Gamescope, the Systemd user socket should always be available. Maybe Decky loads too early. I guess I could try adding a retry logic.

[theCapypara]

@fsworld009 Please note that Bazzite isn't supported by the plugin. It could be that it does session handling different. If this is only happening on Bazzite, it's maybe something that they need to change.

[theCapypara]

The newest plugin update adds some resilience to errors, the plugin may load better under Bazzite now.
See this PR of the pending plugin update submission: SteamDeckHomebrew/decky-plugin-database#727
(always looking for test reports there to get it released sooner :) )