From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] glib v2.74: When copying files using Thunar from android device to void system they arrive without time / date stamp. Going back to v2.72 solves this problem.
Date: Fri, 09 Dec 2022 21:23:36 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40990@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
New issue by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/40990
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.17_1 x86_64 GenuineIntel uptodate hold rrmDFFFFFFF
### Package(s) Affected
glib-2.74.0_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Only aware of this mention in a now closed issue:
https://github.com/void-linux/void-packages/issues/39523#issuecomment-1267932816
### Expected behaviour
Copying a file from an android device to the void system using thunar should not result in the file on the void system having a blank date / time entry. The date / time stamp of the file should be the same as on the android device.
### Actual behaviour
When copying a file using Thunar from android device to void system the files arrives without time / date stamp.
This does not occur if terminal is used (cp -p).
If terminal is used to view file attributes (ls-l) the file copied using Thunar has a date / time stamp of Jan 1, 1970 and the attributes "-rwxr-----". The file copied using terminal (cp -p) the file has the same date / time stamp as the file on the android device and the attributes "-rw-------".
When showing of attributes is enabled in Thunar, it shows the same respective attributes as "ls -l" command (as it should).
### Steps to reproduce
- Connect android device and allow file access.
- Copy a file using Thunar from the android device to the void system.
- If glib (and glib-networking) v2.74 is installed, the file has no date / time stamp on the void system.
- If glib (and glib-networking) v2.72 is installed, the file shows the same date / time stamp as file on android device.
next reply other threads:[~2022-12-09 20:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 20:23 gc-user [this message]
2022-12-13 16:13 ` glib v2.74: When copying files using Thunar from android device to void system they arrive with file attributes reset to default (time / date stamp, permissions). " sgn
2022-12-14 9:26 ` gc-user
2022-12-14 13:44 ` sgn
2022-12-14 13:47 ` sgn
2022-12-14 13:49 ` sgn
2022-12-14 17:54 ` gc-user
2022-12-14 17:55 ` gc-user
2022-12-14 17:57 ` paper42
2022-12-15 2:00 ` sgn
2022-12-15 9:54 ` gc-user
2022-12-15 10:21 ` sgn
2022-12-15 10:22 ` sgn
2022-12-15 10:29 ` gc-user
2022-12-15 10:30 ` gc-user
2022-12-15 10:32 ` gc-user
2022-12-16 16:24 ` sgn
2022-12-16 18:43 ` gc-user
2022-12-16 19:03 ` [ISSUE] [CLOSED] " classabbyamp
2022-12-16 19:04 ` gc-user
2022-12-17 17:54 ` sgn
2022-12-18 11:14 ` gc-user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40990@inbox.vuxu.org \
--to=gc-user@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).