I can't access my anime library

[Yukinooooooo]

I'm using :
Fedora Linux 39 KDE Plasma
KDE Plasma Version : 5.27.10
KDE Frameworks Version : 5.111.0
Qt Version : 5.15.11
Kernel Version : 6.6.8
Wayland

I can't access my anime library due to an unknown reason. Usually it works fine except now my trackma-gtk window is still displayed like a few days

[dyskette]

If you start it from the terminal what messages does it display?

[Yukinooooooo]

If you start it from the terminal what messages does it display?

When I type trackma-gtk on the terminal, it gives the result

Trackma GTK v0.8.6
Engine: Trackma v0.8.6 - using account my email (kitsu).
Engine: Reading config files...
Data: Initializing...
libkitsu: Initializing...
Data: Using libkitsu (anime)
Engine: Parsing redirection file...
Engine: Scanning local library...

[dyskette]

Well, if you are ok with this, you could try clearing the accounts/config and adding them again.

1. Close trackma.
2. Rename the directory ~/.config/trackma to something else.
3. Open trackma and add the accounts, set your configuration.

That at least should get you out of that state.

[Yukinooooooo]

Well, if you are ok with this, you could try clearing the accounts/config and adding them again.

1. Close trackma.

2. Rename the directory `~/.config/trackma` to something else.

3. Open trackma and add the accounts, set your configuration.

That at least should get you out of that state.

I followed your advice, it worked wonderfully. I removed my account on trackma-gtk, then I deleted the trackma folder located in ~/.config/trackma then I reopened trackma-gtk then added my account, there I have access to my library anime

Thank you very much for the advice and for creating a Trackma application

[FichteFoll]

If you still have the old trackma config directory, could you try restoring it temporarily and launching trackma additionally with the -d flag to enable debug logging? I'm not convinced that will yield more clues, but it may.

Otherwise we'll need to close the issue since there is nothing we can do to debug this problem without further info.