Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files not loaded into the database #10613

Closed
mixxxbot opened this issue Aug 23, 2022 · 10 comments
Closed

Files not loaded into the database #10613

mixxxbot opened this issue Aug 23, 2022 · 10 comments
Labels
incomplete stale Stale issues that haven't been updated for a long time.

Comments

@mixxxbot
Copy link
Collaborator

Reported by: soundflyer
Date: 2021-12-10T14:40:57Z
Status: New
Importance: Undecided
Launchpad Issue: lp1954453


In the case of used special characters in the filename, the files will be not loaded into the database.

for example,
I try to load a file name "DJ Ötzi - irgendein Lied" but it will be not displayed in the track list.
The same problem I have with kyrillic characters in the filenames.
All these files will be not displayed.

OS: Linux x86_64 Ubuntu Studio 20.04
Mixxx: 2.3.1

@mixxxbot
Copy link
Collaborator Author

Commented by: uklotzde
Date: 2021-12-10T15:10:41Z


There are known issues on macOS: https://bugs.launchpad.net/mixxx/+bug/1866067

On Linux I cannot confirm this. Everything works as expected and all kinds of special characters in file names are handled correctly. At least on Fedora.

@mixxxbot
Copy link
Collaborator Author

Commented by: soundflyer
Date: 2021-12-10T15:51:52Z


I tested with 4 files.
1 file normal characters
3 file with different characters (german special characters like öäü and kyrillic characters).
In the database only the file without the special characters will be displayed.
Thats strange....

@mixxxbot
Copy link
Collaborator Author

Commented by: uklotzde
Date: 2021-12-10T16:09:31Z


Please check the log file for any warnings.

This should not be an issue on any recent Linux distribution that uses UTF-8. Internally Qt uses UTF-16, which also includes all the characters you mentioned.

@mixxxbot
Copy link
Collaborator Author

Commented by: soundflyer
Date: 2021-12-13T07:46:11Z


Maybe I found the Problem.
I'm using a NAS. If I'm connected via Windows to this NAS system, all files will be displayed with the correct characters. If I try to use the connection via a Linux system, the special characters are changed to "very" special signs. These signs are not readable (thats what I think) in Mixxx.

Now I have to find a solution for Linux for to display the correct file names with special characters
OR
I have to rename all file names (replace the special characters) in the NAS itself.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2021-12-13T21:44:22Z


are changed to "very" special signs

Is only the library scanner failing to pick them up or is it also failing if you try to drop such a file into a deck.

Please attach the ~/.mixxx/mixxx.log file here from this attempt.

Does the Linux File manager display the special characters tracks correctly?

Please also open a texts editor, drop the file to it.
The file:// url should be displayed. Save this file and attache it here as well.

Thank you.

@mixxxbot
Copy link
Collaborator Author

Commented by: soundflyer
Date: 2021-12-15T10:01:05Z


short update
in the Linux file manager I have the same problem.
äöü will be displayed as an special sign. It looks like a black traffic sign with questions mark.

If i have more time, I will make more tests as descripted in our message above and I will send you the log.

@mixxxbot
Copy link
Collaborator Author

Commented by: ehmic
Date: 2021-12-19T15:21:31Z


If files with special characters like Umlauts (öä.. etc) are displayed correctly when stored on your harddrive (or SSD), I guess the issue is either, that the problematic filenames contain a byte sequence that isn't valid UTF, or something is strange/wrong with the way how your Ubuntu connects to the NAS.

But if you are experiencing this also with local files stored on your HDD/SSD, or while typing in the terminal / text editor, it is more likely a problem with your locales.

See for example the thread below and check if your locales appear to be messed up.

https://unix.stackexchange.com/questions/425929/problems-with-umlauts-cant-type-in-terminal-cant-open-files

If so, try to reconfigure them. ('sudo dpkg-reconfigure locales' should do the trick on Ubuntu)

Anyhow, if the problem also occurs in your file manager, I would say it is almost certainly not a bug in Mixxx.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@foss-
Copy link
Contributor

foss- commented Mar 27, 2023

Is this still reproducible with 2.3.4 on Linux?

@daschuer
Copy link
Member

This is also related: #11103

@github-actions github-actions bot added the stale Stale issues that haven't been updated for a long time. label May 27, 2023
@github-actions
Copy link

Expired for Mixxx because there has been no activity for 60 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete stale Stale issues that haven't been updated for a long time.
Projects
None yet
Development

No branches or pull requests

3 participants