Description of problem: exa seems to crash with very old dates. Not sure why I'm getting these old dates but that is a separate issue with "hugo". Version-Release number of selected component (if applicable): exa-0.9.0-9.fc32.x86_64 How reproducible: Every time Steps to Reproduce: $ touch -t 190101010000 a $ exa -l Actual results: $ touch -t 190101010000 a $ exa -l thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: SystemTimeError(2147483648s)', src/fs/file.rs:331:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace zsh: abort (core dumped) exa -l % RUST_BACKTRACE=1 exa -l thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: SystemTimeError(2147483648s)', src/fs/file.rs:331:9 stack backtrace: 0: <unknown> 1: <unknown> 2: <unknown> 3: <unknown> 4: <unknown> 5: <unknown> 6: <unknown> 7: <unknown> 8: <unknown> 9: <unknown> 10: <unknown> 11: <unknown> 12: <unknown> 13: <unknown> 14: start_thread 15: __GI___clone note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. zsh: abort (core dumped) RUST_BACKTRACE=1 exa -l $ RUST_BACKTRACE=full exa -l thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: SystemTimeError(2147483648s)', src/fs/file.rs:331:9 stack backtrace: 0: 0x55c40a3b4496 - <unknown> 1: 0x55c40a35358c - <unknown> 2: 0x55c40a3b3d06 - <unknown> 3: 0x55c40a3b39eb - <unknown> 4: 0x55c40a3b336f - <unknown> 5: 0x55c40a3b2f4a - <unknown> 6: 0x55c40a351fa0 - <unknown> 7: 0x55c40a354572 - <unknown> 8: 0x55c40a384a9b - <unknown> 9: 0x55c40a37e56e - <unknown> 10: 0x55c40a3ae866 - <unknown> 11: 0x55c40a3ad95c - <unknown> 12: 0x55c40a3bd55e - <unknown> 13: 0x55c40a3be1d8 - <unknown> 14: 0x7fe1e5819432 - start_thread 15: 0x7fe1e572c913 - __GI___clone 16: 0x0 - <unknown> zsh: abort (core dumped) RUST_BACKTRACE=full exa -l $ ls -l total 0 -rw-r--r--. 1 paul paul 0 Dec 13 1901 a $ stat a File: a Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 16783757 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ paul) Gid: ( 1000/ paul) Context: unconfined_u:object_r:user_home_t:s0 Access: 1901-12-13 20:45:52.000000000 +0000 Modify: 1901-12-13 20:45:52.000000000 +0000 Change: 2020-10-10 16:29:52.178485001 +0100 Birth: - Expected results: No crash and a directory listing
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.