File path with symbols not supported by the Windows system

doblerone · 2021-05-29 07:20:40

After installing seafile-client, I can see that some folder are not synchronized because of the following error:
"The file path contains symbols that are not supported by the Windows system".

My system is configured in spanish and I have check the configuration in Plasma and everything looks fine, language-wise, but still I'm missing something.
Some of the config files I've checked:

locale
LANG=es_ES.UTF-8
LC_CTYPE="es_ES.UTF-8"
LC_NUMERIC="es_ES.UTF-8"
LC_TIME="es_ES.UTF-8"
LC_COLLATE="es_ES.UTF-8"
LC_MONETARY="es_ES.UTF-8"
LC_MESSAGES="es_ES.UTF-8"
LC_PAPER="es_ES.UTF-8"
LC_NAME="es_ES.UTF-8"
LC_ADDRESS="es_ES.UTF-8"
LC_TELEPHONE="es_ES.UTF-8"
LC_MEASUREMENT="es_ES.UTF-8"
LC_IDENTIFICATION="es_ES.UTF-8"
LC_ALL=

 locale -a
C
es_ES.utf8
POSIX

localectl
   System Locale: LANG=es_ES.UTF-8
       VC Keymap: es
      X11 Layout: es
       X11 Model: pc104

hostnamectl
 Static hostname: arch
       Icon name: computer-desktop
         Chassis: desktop
      Machine ID: bd8b73dec87d4fa0a016266295994559
         Boot ID: 2eb0efacfe2948cf8ff20469e8662cfc
Operating System: Arch Linux                      
          Kernel: Linux 5.12.7-arch1-1
    Architecture: x86-64
 Hardware Vendor: System manufacturer
  Hardware Model: System Product Name

Am I missing something else?

Thx in advance

Last edited by doblerone (2021-05-30 11:03:18)

seth · 2021-05-29 07:37:02

Which "file path"?

My system is configured in spanish and I have check the configuration in Plasma and everything looks fine, language-wise, but still I'm missing something.

I don't use seafile, but assume that this has nothing to do with *your* system but a protection against filenames that are invalid on windows:
https://en.wikipedia.org/wiki/Filename#In_Windows

doblerone · 2021-05-29 07:44:24

That's what I'm trying to figure out For example, this file seems to be problematic:
"Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html"

P.S: All my machines are running Linux and I'm only getting that error in ArchLinux.

seth · 2021-05-29 08:09:34

https://fossies.org/linux/seafile/daemon/repo-mgr.c

 1219 static gboolean
 1220 check_path_ignore_on_windows (const char *file_path)
 1221 {
 1222     gboolean ret = FALSE;
 1223     static char illegals[] = {'\\', ':', '*', '?', '"', '<', '>', '|', '\b', '\t'};
 1224     char **components = g_strsplit (file_path, "/", -1);
 1225     int n_comps = g_strv_length (components);
 1226     int j = 0;
 1227     char *file_name;
 1228     int i;
 1229     char c;
 1230 
 1231     for (; j < n_comps; ++j) {
 1232         file_name = components[j];
 1233 
 1234         if (has_trailing_space_or_period (file_name)) {
 1235             /* Ignore files/dir whose path has trailing spaces. It would cause
 1236              * problem on windows. */
 1237             /* g_debug ("ignore '%s' which contains trailing space in path\n", path); */
 1238             ret = TRUE;
 1239             goto out;
 1240         }
 1241 
 1242         for (i = 0; i < G_N_ELEMENTS(illegals); i++) {
 1243             if (strchr (file_name, illegals[i])) {
 1244                 ret = TRUE;
 1245                 goto out;
 1246             }
 1247         }
 1248 
 1249         for (c = 1; c <= 31; c++) {
 1250             if (strchr (file_name, c)) {
 1251                 ret = TRUE;
 1252                 goto out;
 1253             }
 1254         }
 1255     }
 1256 
 1257 out:
 1258     g_strfreev (components);
 1259 
 1260     return ret;
 1261 }
 1262 #endif

I don't see any problem w/ the path you posted (except for the quotes), but oc. there could be a trailing whitespace being lost in copy and paste and the nonprintable chars are not printable.

doblerone · 2021-05-29 08:15:06

Thx @seth for your replies.

ATM, I'm closing the thread because it seems to be a problem with the client itself:
https://forum.seafile.com/t/8-0-2-pop-u … dows/14561

seth · 2021-05-29 15:58:11

You should probably be able to tell it to ignore that, because you're not using windows, but that doesn't explain why it thinks the filename isn't windows compatible.
Check

ls -b "Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html"

for non-printable chars.

Edit: please don't mark threads as "closed", that's for mods when they lock a thread.

Last edited by seth (2021-05-29 15:58:41)

doblerone · 2021-05-30 11:06:15

seth wrote:

You should probably be able to tell it to ignore that, because you're not using windows, but that doesn't explain why it thinks the filename isn't windows compatible.
Check
ls -b "Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html"
for non-printable chars.
Edit: please don't mark threads as "closed", that's for mods when they lock a thread.

Nothing looks suspicious in the file:

ls -b "Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html"
Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html

As said before, it looks like a bug in the client application as more and more people are complaining about this behaviour.

seth · 2021-05-30 12:29:51

https://github.com/haiwen/seafile/issues/2451

I get that this is *also* just annoying, but you probably want to tell them that there seems a bigger issue at hand.
Because either the routine hits some false positives (and I really don't see how unless there's some stack corruption somewhere) or the server responds bogus error codes.
Ie. there's a bug *beyond* "i don't use windows and don't care".

Flemur · 2021-05-30 13:10:30

doblerone wrote:

That's what I'm trying to figure out For example, this file seems to be problematic:
"Linux_academy/Python_sysadmins/05__Creating_a_Larger_Scripting_Project/01__Planning_&_Project_Structure/03__Initial_Project_Layout.html"

FWIW:

$ mkdir 01__Planning_&_Project_Structure
[1] 4864
zsh: command not found: _Project_Structure
$  
[1]  + done       mkdir 01__Planning_
$

seth · 2021-05-30 14:19:32

& is obviously a keyword in zsh/bash, so you have to escape or quote it at the shell - but that has no relevance to the actual filename restrictions.

mkdir '01__Planning_&_Project_Structure'

will generate a directory that is named 01__Planning_&_Project_Structure, not 01__Planning_\&_Project_Structure

Lone_Wolf · 2026-05-05 08:25:43

Moderator Note

necro-bumping spam post deleted, also closing thread.

Arch Linux

#1 2021-05-29 07:20:40

File path with symbols not supported by the Windows system

#2 2021-05-29 07:37:02

Re: File path with symbols not supported by the Windows system

#3 2021-05-29 07:44:24

Re: File path with symbols not supported by the Windows system

#4 2021-05-29 08:09:34

Re: File path with symbols not supported by the Windows system

#5 2021-05-29 08:15:06

Re: File path with symbols not supported by the Windows system

#6 2021-05-29 15:58:11

Re: File path with symbols not supported by the Windows system

#7 2021-05-30 11:06:15

Re: File path with symbols not supported by the Windows system

#8 2021-05-30 12:29:51

Re: File path with symbols not supported by the Windows system

#9 2021-05-30 13:10:30

Re: File path with symbols not supported by the Windows system

#10 2021-05-30 14:19:32

Re: File path with symbols not supported by the Windows system

#11 2026-05-05 08:25:43

Re: File path with symbols not supported by the Windows system

Board footer