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

[Bug] Selecting a folder to exclude freezes the settings #13

Open
Barraguesh opened this issue Nov 30, 2021 · 11 comments
Open

[Bug] Selecting a folder to exclude freezes the settings #13

Barraguesh opened this issue Nov 30, 2021 · 11 comments

Comments

@Barraguesh
Copy link

Steps to reproduce: Go to settings, Advanced, in the exclusion section chose "Add", "Choose folder". After selecting one it freezes and no action can be performed, neither closing the settings nor the dialog. The app seems to be syncing and downloading the background without problem.

Distro: Fedora 35 GNOME.

Doesn't happen with upstream "rpm", switched to it meanwhile.

@RamonAbudAlcala
Copy link

Same happening here.

Distro: Debian 12 GNOME

Also when trying to change default download or upload folder.

@johnny32
Copy link

johnny32 commented Jan 1, 2024

Same here when trying to set a different path for the full syncing. It looks like it freezes whenever you change any of the default directories.

Distro: Fedora 39 KDE

@vermarine
Copy link

Same here with Fedora 39 silverblue: trying to do anything that brings up the file picker completely freezes up megasync, rendering me unable to use selective sync since I cannot select a folder. I tried giving access to my entire home directory via flatseal, but to no avail

@ZhengshuaiPENG
Copy link

I can confirm with Linux Mint 21.3 Cinamon

@sudoshindo
Copy link

Nothing? Anything at all? Nobody knows if this is an upstream issue or packaging issue?

@DenysMb
Copy link

DenysMb commented Jul 10, 2024

It's a packaging issue, as the same doesn't happen in the non-Flatpak version.

But the maintainer says that it is a packaging issue (he said it here: #76 (comment)), so I think it will never be fixed until someone open a PR to fix this.

@loukamb
Copy link

loukamb commented Jul 12, 2024

It is entirely a packaging issue. The maintainer, however, does not know what causes it.

@jasongodev
Copy link

jasongodev commented Aug 8, 2024

Just chiming in. I'm trying to look in this issue. I also experience this in Arch Linux.

@jasongodev
Copy link

I successfully made a new flatpak manifest that fixes a lot of packaging issues including this bug. Just waiting for the merge.

#94

@zunjack

This comment was marked as abuse.

@jasongodev
Copy link

@zunjack We already agreed that patch files are the way to go so no more regex in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

11 participants