Using %e or %k in custom date format result in Thunar displaying current time in place of file modified time

Bug #1880621 reported by halogen2
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Triaged
Undecided
Unassigned
Focal
Triaged
Undecided
Unassigned
Impish
Fix Released
Undecided
Unassigned

Bug Description

Xubuntu 20.04 live CD

Steps to reproduce:

1) Edit > Preferences > Date > Format, pick the "yyyy-mm-dd hh:mm:ss" option from the drop-down

2) Right-click any file (e.g. /usr/lib/chroot-setup.sh) > Properties. Note the modified and accessed times. Close the Properties dialog.

3) Back to Edit > Preferences, pick Custom date format. Set to:

%e %b %Y, %k:%M:%S

4) right-click the same file again > Properties

Expected results:

Same dates/times should be displayed at (2) and (4), just in different format.

Actual results:

At (4), the current date/time is displayed for Modified and Accessed.

Using stat in Terminal shows the times displayed with the preset option are the correct ones.

If I A) replace %e with %d, AND B) replace %k with %H, so the custom format becomes:

%d %b %Y, %H:%M:%S

Thunar does show correct dates/times with that custom format. Replacing only %e (keeping %k) results in Thunar showing correct date with completely wrong time.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: thunar 1.8.14-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CurrentDesktop: XFCE
Date: Tue May 26 00:23:52 2020
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
halogen2 (halogen2) wrote :
description: updated
halogen2 (halogen2)
description: updated
description: updated
Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :
Revision history for this message
halogen2 (halogen2) wrote :

Sorry for the late reply, I thought I had already replied to comment 2.

Indeed the upstream patch linked in comment 2 fixes this issue. Thanks @lastonestanding !

Can this please be SRU'd to focal?

Revision history for this message
Sean Davis (bluesabre) wrote :

Fixed in thunar 4.15.3 and 1.8.16

Changed in thunar (Ubuntu Impish):
status: New → Fix Released
Changed in thunar (Ubuntu Focal):
status: New → Triaged
Changed in thunar (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.