Bug 180360
Summary: | digikam won't accept new pictures or allow overwrites | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bob Agel <cragel> |
Component: | digikam | Assignee: | Marcin Garski <mgarski> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-04 10:17:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bob Agel
2006-02-07 15:42:12 UTC
1. "Clicking on the overwrite button returns no result." It returns result, but thumbnail isn't refreshed so you don't see it, if you try to view overwriten picture you will see the new one. That's digikam bug: http://bugs.kde.org/113797 2. Yes, currently there isn't documentation (in FE) for digikam. 1. Afraid that's not the case. Attempted to overwrite dscn0356.jpg (example) - properties show 'modified 1/8/2006', 'accessed 2/8/2006' - While attempting to overwrite, each time would get the same error "access denied" (see above). Also, when trying to view dscn0358.jpg - dscn0365.jpg which are in the same album, digikam refuses to recognize them and right-clicking on each pic and choosing digikam for viewing simply stalls, however can be viewed with any other viewer such as Kuickshow, Kview, Gwenview, Gimp & Showfoto. Digikam also will not create any new albums. Update to digikam today resulted in no change. Could you create a new user in your system, log into it and then try use digikam? FYI Access denied message isn't releated with /usr/bin/digikam, but probably digikam can't write to digikam's databse (digikam3.db file) or some directories in your home directory. You're on target with that. Under a new user, digikam acts correctly. Now, I'll have to do some research to find which files are involved. Thanks! chmod -R 777 on /home/username/pictures did the trick. Thanks again! |