From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: 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). Going back to v2.72 solves this problem.
Date: Wed, 14 Dec 2022 10:26:18 +0100 [thread overview]
Message-ID: <20221214092618.F6PiR0YTP2oJDuF2Em3LmH_qKxypwWn_h0ybIDmQ_Uc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40990@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/40990#issuecomment-1350714238
Comment:
Thanks for testing and making a video of it!
I'm using https://repo-default.voidlinux.org/current for install and updates, so I would assume my system has the default void linux glib.
I tried an older thunar version (4.16.8 instead of 4.16.11) to make sure it's not thunar. Same error.
Also, I started thunar from terminal once in the past to see if any error messages or warning would show up and give me clue as to what process might be responsible, but there were no messages at all.
I can't tell which (other) circumstances might play a role here.
- Android version of android device? (7.1)
- File system on receiving side? (zfs)
- Packages connected to linux-android interaction, like *mtp*, *android* in package name that might interfere with each other and cause (indirectly) problems with newer glib? (installed are: go-mtpfs-1.0.0_1, gvfs-mtp-1.50.2_1, jmtpfs-0.5_1, libmtp-1.1.20_1, mtpfs-1.1_4, simple-mtpfs-0.4.0_1, android-tools-33.0.3p1_1)
next prev parent reply other threads:[~2022-12-14 9:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 20:23 [ISSUE] glib v2.74: When copying files using Thunar from android device to void system they arrive without time / date stamp. " gc-user
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 [this message]
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=20221214092618.F6PiR0YTP2oJDuF2Em3LmH_qKxypwWn_h0ybIDmQ_Uc@z \
--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).