Bug 416995 - "Permissions" tab is not immediately updated after I change ownership via CLI
Summary: "Permissions" tab is not immediately updated after I change ownership via CLI
Status: REOPENED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Properties dialog (show other bugs)
Version: 5.66.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 436961 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-01-31 19:32 UTC by Patrick Silva
Modified: 2021-05-30 21:17 UTC (History)
3 users (show)

See Also:
Latest Commit: https://invent.kde.org/frameworks/kio/-/commit/057062432b4b5cc4f4fa27990dcde60d3eafa758
Version Fixed In: 5.82

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-01-31 19:32:33 UTC 
STEPS TO REPRODUCE
1. open Dolphin
2. right click on any folder/file present in current location, choose "Properties", click on "Permissions" tab and observe current user and group on bottom
3. close "Properties" window
2. change the ownership of the folder/file observed in the step 2
via CLI with chown or chgrp commands
3. now check the ownership of the same file/folder via Dolphin: we see the same ownership observed in the step 2
4. press F5 and check the ownership via Dolphin again: now the "Permissions" tab shows
updated ownership

EXPECTED RESULT
"Permissions" tab always shows updated ownership

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Comment 2 Patrick Silva 2021-04-23 12:43:44 UTC 
it's still reproducible.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.21.80
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 3 Ahmad Samir 2021-04-24 10:29:47 UTC 
Right, reading the steps to reproduce again I see it's a different issue; sorry for the noise. :|
Comment 4 Patrick Silva 2021-05-30 21:17:04 UTC 
*** Bug 436961 has been marked as a duplicate of this bug. ***