[dolphin] [Bug 495649] New: Dolphin's "Properties for …" dialog should allow editing the timestamps
ratijas
bugzilla_noreply at kde.org
Thu Oct 31 16:58:28 GMT 2024
https://bugs.kde.org/show_bug.cgi?id=495649
Bug ID: 495649
Summary: Dolphin's "Properties for …" dialog should allow
editing the timestamps
Classification: Applications
Product: dolphin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: me at ratijas.tk
CC: kfm-devel at kde.org
Target Milestone: ---
Created attachment 175412
--> https://bugs.kde.org/attachment.cgi?id=175412&action=edit
mtime September 22, 1881
SUMMARY
Dolphin's "Properties for …" dialog should allow editing the timestamps if the
file system permissions allow it.
Use case: I unpacked the "drivers" archive downloaded from my monitor's vendor
website, and for some reason the directory where an ICC color profile was
contained has Modification Time set to Thursday, September 22, 1881 5:20:31 AM.
So now NextCloud totally refuses to sync it, and there is no GUI button to fix
it, and somehow it is my problem now to google how to change `mtime` on Linux
(assuming I know what `mtime` is already).
This is obviously both a vendor error and NextCloud error. But Dolphin could've
made it easier for user to resolve this situation.
STEPS TO REPRODUCE
1. Open file or directory properties for something writable by the current
user.
OBSERVED RESULT
Created, Modified and Accessed timestamps are read-only text labels.
EXPECTED RESULT
Timestamps could have an option to edit them.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.4-arch1-1 (64-bit)
file system: btrfs
mount options: rw,relatime,ssd,discard=async,space_cache=v2,subvol=/@home
ADDITIONAL INFORMATION
You can get the funny archive here, under the Drivers tab:
https://aoc.com/al-en/gaming/products/monitors/u28g2xu-bk/downloads
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list