https://bugs.kde.org/show_bug.cgi?id=404777
Alex Bikadorov <alex.bikado...@kdemail.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nikita+...@melnichenko.name
--- Comment #2 from Alex Bikadorov <alex.bikado...@kdemail.net> ---
@Nikita let's continue part of the discussion here.
Nikita's comment:
> I checked KIO::CopyJob::setDefaultPermissions and follow up code and this
> piece looks suspicious:
>
> filecopyjob.cpp:
> 501 if (d->m_mustChmod) {
> 502 // If d->m_permissions == -1, keep the default permissions
> 503 if (d->m_permissions != -1) {
> 504 d->m_chmodJob = chmod(d->m_dest, d->m_permissions);
> 505 addSubjob(d->m_chmodJob);
> 506 }
> 507 d->m_mustChmod = false;
> 508 }
>
> Haven't debugged though since KIO likely requires special debugging
> environment but according to the code (d->m_permissions == -1) is exactly
> happens after we call setDefaultPermissions and then chmod is never called.
>
...
>
> Probably, we should look more into the Dolphin code. They get around it
> somehow.
Dolphin uses KIO for creating new files (-> filewidgets/knewfilemenu.cpp) and
there is the same problem here. Umask is ignored, the default file permission
for new text files is alwas -rw-r--r-- and nobody noticed yet.
@Nate
Happy to try it - as soon as I've figured out how to build and install KIO and
dependencies into a custom directory without affecting my system. I'm not that
good with the cmake/make.
--
You are receiving this mail because:
You are watching all bug changes.
