https://bugs.kde.org/show_bug.cgi?id=395609
--- Comment #9 from Nikita Melnichenko <nikita+...@melnichenko.name> ---
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.
So far I think the best way is to handle local files differently and create
them with QFile to get the default permissions. The downside is that it should
be handled carefully given the async nature of that code.
Probably, we should look more into the Dolphin code. They get around it
somehow.
--
You are receiving this mail because:
You are watching all bug changes.
