Skip to content
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

Element session/data corrupts when autostarting the application on Linux (Fedora) #1945

Closed
kees-closed opened this issue Oct 22, 2024 · 1 comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@kees-closed
Copy link

kees-closed commented Oct 22, 2024

Steps to reproduce

  1. Where are you starting? What can you see?
    In my ~/.config/autostart I've put a symlink to the Flatpak desktop file (/var/lib/flatpak/exports/share/applications/im.riot.Riot.desktop) to autostart Element when logging in. However, this often kills Element. It gets stuck:

image

When I don't autostart it, this doesn't happen.

Because it gets stuck early, I cannot generate a debug file. After I force close Element, it lost the session and I have to login again and reconfigure some settings. This is not great of course. Is there a way to generate a log usable for debugging when it's stuck in the loading process?

image

Outcome

See above.

Operating system

Fedora 40

Application version

Element im.riot.Riot 1.11.81 stable flathub system

How did you install the app?

Flatpak

Homeserver

matrix.surf.nl

Will you send logs?

No

@t3chguy
Copy link
Member

t3chguy commented Oct 22, 2024

The flatpak is not a package we maintain, the repo for it is https://github.com/flathub/im.riot.Riot/

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Oct 22, 2024
@dosubot dosubot bot added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants