QFile permission not reporting correctly

ocgltd

@sierdzio They both report the exact same WRONG permissions. (Seems strange)

SGaist

Hi,

I am wondering if there's not some cache that is used to store that information and your are accessing it again after the permission changed.

ocgltd

@SGaist I don't think so...simple SATA disk, no hardware cache inbetween. Software wise, just plain old linux...

Or are you saying Qt might have a cache?

JonB

@ocgltd said in QFile permission not reporting correctly:

Or are you saying Qt might have a cache?

It might do, to speed repeated calls to the same file. The strange thing is it would not be surprising if you changing it externally via chmod did not make it update a cache it might have. But you would have thought that with myFile.setPermissions(perm) it would know to update any myFile.permissions() cached value correspondingly.

ocgltd

@JonB Yeah, if I changed via command line and Qt didn't see the change then I would suspect a cache. But if writing permissions from Qt I would expect it to update any Qt cache. I would have guess bug, but both QFile and QFileInfo suffering from the same bug makes me think I'm doing something wrong

sierdzio

Please report this on Qt bug tracker.

JonB

@ocgltd , @sierdzio
I checked this on my Ubuntu 20.04, Qt5.15, and it does indeed behave as you say. So then I looked and found bug QFile::permissions() returns old, cached value after call to QFile::setPermissions() on the same QFile object, Qt 4.6, Unresolved:

I can understand why QFile would not detect changes to the file's permissions outside of the QFile object, although if the permissions
change is done via QFile::setPermissions() then the object can clear its cached value automatically.
Alternatively, the fact that permissions() returns a cached value should be documented.

A related issue is that there is no explicit refresh() method for QFile as there is for QFileInfo, although QFile::exists() does trigger a refresh when called

This task is old and has been idle for a long time. It is therefore being closed on the assumption that it will not be addressed in the foreseeable future. If you really do care about this task, you may reopen it and vote for it.

It was created in 2010 and last updated in 2016. We agree it's a bit bad. You will have to use some alternative, e.g. maybe the static QFile permissions methods work, or the QFileInfo ones.

sierdzio

Oh my, this should have been fixed, not closed :o

Christian Ehrlicher

Reopened: https://bugreports.qt.io/browse/QTBUG-7211

sierdzio

Thanks! Voted.

Christian Ehrlicher

There is also already a patch for it... sometimes it's interesting to see how long bugs linger around and then a small change (here: chooinsg the correct maintainer) suddenly fixes it :)

HoMa

I guess you can just use the static function!?

JonB

@HoMa
I suggested earlier that the OP could try that, but there is no guarantee it will behave any differently. The cache may be by filepath, not by QFile/QFileInfo instance, we don't know.

HoMa

@JonB Sorry - I missed that.

JonB

@HoMa Not a problem :) I'm just saying it may or may not make any difference! But worth a try.

ocgltd

@JonB I'll use the workaround thanks. I couldn't imagine I found such a bug..so I assumed it must be my code.

JonB

@ocgltd said in QFile permission not reporting correctly:

I couldn't imagine I found such a bug.

You produced a simple example, minimal code, clear output to show bad behaviour. If everybody did similar that would be really great :)