Bug 290704 - gwenview_importer creates write-protected files
Summary: gwenview_importer creates write-protected files
Status: RESOLVED DUPLICATE of bug 183159
Alias: None
Product: gwenview
Classification: Applications
Component: importer (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 15:45 UTC by Angelo Naselli
Modified: 2018-08-05 22:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angelo Naselli 2012-01-05 15:45:48 UTC
Version:           unspecified (using KDE 4.7.4) 
OS:                Linux

From:
https://bugs.mageia.org/show_bug.cgi?id=4030




Reproducible: Didn't try

Steps to Reproduce:
1. import photos from camera with gwenview_importer
2. open folder where photos are imported with gwenview
3. rotate photos you need to
4. save changes


Actual Results:  
all the files are created with 444 permission.

Expected Results:  
expected permissions should be 644 as umask.
Comment 1 Richard Neill 2014-08-18 18:17:43 UTC
Still a bug in KDE 4.13.3 (Kubuntu Trusty) as of Sept 2014.
Comment 2 null 2017-10-16 21:31:17 UTC
Thanks for reporting. I can confirm the behaviour even with the KF5 based importer introduced with KDE Applications 17.04.

Details:
- Importing from a local directory with r/w images results in r/w images
- Importing from a local directory with r/- images results in r/- images which cannot be modified
- Importing via camera:/ (e.g. from an Android device) results in r/- images, suggesting the kioslave provides a r/- view of the device

Possible solution: Write r/w images in every case (or better: respect the default umask). However, I wonder whether this should be solved at the kioslave level, as this also happens when copying in Dolphin).
Comment 3 null 2018-08-05 22:40:43 UTC

*** This bug has been marked as a duplicate of bug 183159 ***