8000 Created unreadable backup library file · Issue #18760 · darktable-org/darktable · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Created unreadable backup library file #18760

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

Closed
1 task done
hadess opened this issue May 5, 2025 · 8 comments · Fixed by #18837
Closed
1 task done

Created unreadable backup library file #18760

hadess opened this issue May 5, 2025 · 8 comments · Fixed by #18837

Comments

@hadess
Copy link
hadess commented May 5, 2025

Is there an existing issue for this?

  • I checked and did not find my issue in the already reported ones

Describe the bug

Darktable created a 0-sized file that's unreadable by my backup software:

$ ls -l /home/hadess/.var/app/org.darktable.Darktable/config/darktable/data.db-pre-5.0.1
--w-------. 1 hadess hadess 0 Apr 30 10:42 /home/hadess/.var/app/org.darktable.Darktable/config/darktable/data.db-pre-5.0.1

Pika/Borg complain:

Warning: /home/hadess/.var/app/org.darktable.Darktable/config/darktable/data.db-pre-5.0.1: open: [Errno 13] Permission denied: 'data.db-pre-5.0.1'

Steps to reproduce

Install Darktable from Flathub and run it.

I don't remember whether I might have installed Darktable previously, but in any case the library file is empty.

Expected behavior

File is readable or doesn't exist

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

Flatpak

darktable version

darktable 5.0.1

What OS are you using?

Linux

What is the version of your OS?

Fedora

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@pehar1
Copy link
pehar1 commented May 5, 2025

open: [Errno 13] Permission denied: 'data.db-pre-5.0.1'

Check your file permissions and the permissions of your backup software to access flatpack related files.

@hadess
Copy link
Author
hadess commented May 5, 2025

Check your file permissions and the permissions of your backup software to access flatpack related files.

This isn't helpful, I know how to change permissions, or delete the file. The permissions are here:

$ ls -l /home/hadess/.var/app/org.darktable.Darktable/config/darktable/data.db-pre-5.0.1
--w-------. 1 hadess hadess 0 Apr 30 10:42 /home/hadess/.var/app/org.darktable.Darktable/config/darktable/data.db-pre-5.0.1

The file is created in this state by Darktable.

@parafin
Copy link
Member
parafin commented May 5, 2025

According to this:

// there is nothing to backup, create an empty file to prevent further backup attempts
const int fd = g_open(backup, O_CREAT, S_IWUSR);

it is a flag to mark that backup is not needed. No idea why write-only permissions were chosen.

@victoryforce
Copy link
Collaborator

Darktable created a 0-sized file that's unreadable by my backup software:

@hadess You would like to have read access to this file just to get rid of complaints from your backup software, am I correct?

@hadess
Copy link
Author
hadess commented May 5, 2025

@hadess You would like to have read access to this file just to get rid of complaints from your backup software, am I correct?

Given how the file was created, I know how to do that for myself (I'll just chmod the file to also be readable, job done).

I'm filing an issue because it's a problem in Darktable which every new user will run into.

@parafin
Copy link
Member
parafin commented May 5, 2025

It’s a problem only when combined with your backup software, so far from every user will encounter it. And problem itself is very minor - just a warning. File is empty, so it not being readable doesn’t matter much…

@da-phil
Copy link
Contributor
da-phil commented May 10, 2025

I agree with @hadess that it's inconvenient if a program (dt) creates files which do not have read permissions for some reason. Is there any sensible reason why the read permission flag is not set?

@grantx2016
Copy link
grantx2016 commented May 19, 2025

I have this issue and it's wasted a lot of my time trying to figure it out. Please just fix the permissions so that users, who may not know how to change permissions, aren't burdened.

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

Successfully merging a pull request may close this issue.

6 participants
0