Bug 440013 - Dolhin can't auto update folder view when more than 1 tab is restored
Summary: Dolhin can't auto update folder view when more than 1 tab is restored
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: view-engine: general (show other bugs)
Version: 21.04.3
Platform: Manjaro Linux
: NOR minor
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-18 17:38 UTC by TYY331
Modified: 2021-07-18 20:44 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 TYY331 2021-07-18 17:38:23 UTC
SUMMARY

If I use the standard Dolphin settings, where it remembers the previous state on opening, and that previous state happens to have more than one tab opened, Dolphin is unable to update the folder contents on real time (for example creating a file with a text editor on that folder) relying on pressing F5 to update it's content (pressing F5 before I make changes fixes the issue, seems like this "unfreezes" the view). This bug doesn't happen if the remember state option is disabled or the restored state only has one tab opened.

STEPS TO REPRODUCE
1. Use Dolphin default settings for state restore
2. Open more than one tab
3. Close and reopen Dolphin
4. Use a text editor to create a file on the same folder showed by Dolphin on the active tab

OBSERVED RESULT
The folder contents are not updated, the user needs to hit F5 on Dolphin to trigger an update to show the new folder contents, this bug is 100% reproducible.

EXPECTED RESULT
Folder contents should auto update when changes are made to said folder.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE with 5.10 Kernel
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Comment 1 Patrick Silva 2021-07-18 18:04:57 UTC
possibly duplicate if bug 387663
Comment 2 TYY331 2021-07-18 20:44:55 UTC
(In reply to Patrick Silva from comment #1)
> possibly duplicate if bug 387663

I don't really think it's a duplicate since I can fully reproduce the bug and the issues pointed at on that bug report seems really hard to reproduce.