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

Can't open nextcloud todo.txt file #453

Closed
hoshi411 opened this issue Jan 21, 2023 · 4 comments
Closed

Can't open nextcloud todo.txt file #453

hoshi411 opened this issue Jan 21, 2023 · 4 comments
Assignees
Labels
bug Something isn't working no-issue-activity

Comments

@hoshi411
Copy link

Running Sleek version 1.3.0 on Ubuntu Gnome 22.04.1 LTS

I have a todo.txt file hosted in my nextcloud.
I have the files able to access mounted on my Gnome desktop.

In Sleek I click on "open todo.txt" blue button.

I am able to navigate to my todo.txt file mounted on my desktop.

I click "open" after selecting the file.

I expect it to now be synced with Sleek app but nothing at all happens.

@hoshi411 hoshi411 added the bug Something isn't working label Jan 21, 2023
@hoshi411
Copy link
Author

I solved the problem.

I uninstalled the Flatpak version of Sleek and installed 1.3.0 .deb file.

I can now sync with nexcloud todo.txt file.

I am very sad that I cannot use the flatpak version.

@hoshi411
Copy link
Author

I also want to say.

You DEVs are amazing and thank you for this amazing solution which has basically saved my life.

Thank you so much .

@NanoExplorer
Copy link

NanoExplorer commented Jan 24, 2023

Could it be a flatpak issue? I'm not an expert at flatpak, but since it's a sandbox it could be that it doesn't give sleek access. I think flatpak doesn't allow access to mounted volumes by default, and you mentioned you had mounted the nextcloud server. (https://askubuntu.com/questions/1086529/how-to-give-a-flatpak-app-access-to-a-directory)

Edit: other people are having trouble with FlatPak and file access, e.g. #444

My first instinct was that it could be related to #443 , although #443 also affects version 1.3.0 so probably not.

@github-actions
Copy link

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working no-issue-activity
Projects
None yet
Development

No branches or pull requests

3 participants