Did this happend to anyone else?

  • ik5pvx@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    12 days ago

    Can you check in a terminal? If you can see them in the terminal and not in the desktop you’re missing a font. If you can’t see them in the terminal then you’ve somehow mangled them. What was the OS and filesystems you copied from?

  • dragnucs@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    12 days ago

    Never noticed that? How do you copy them, from terminal? What software do you use? What file system do you use?

      • Zikeji@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 days ago

        Are you copying it to a locally mounted ext4 or is it a network share of an ext4 drive, and if so - what type of network share?

      • dragnucs@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        12 days ago

        I cannot reproduce it, I just tried to copy some files with various methods but they always end up correctly named. The only difference is that I have Btrfs. I never encountered this issue when I was using ext4 though.

  • Riskable@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    12 days ago

    Could be a bug in Nautilus though it’s so mature now that would be strange. I’d report it to their repo (don’t have the link and I’m on my phone but it should be easy to find).

    ext4 supports various filename encodings (simultaneously, even!) but sometimes when you copy a file from one destination to another in a batch with mixed encodings you can end up with situations like this. Especially from within a GUI.

    Does the problem occur when you copy each file one by one or only in batch?