after 2.2 MinimServer update following java error: Malformed input or input contains

[seanshankus]

Directly after i updated to 2.2, i'm not getting the following error:
Unexpected exception java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: Vince Guaraldi Trio/A Charlie Brown Christmas/1.10 - Für Elise.flac

I was not getting this in 2.1.2. I suspect it doesn't like "ü" and can change that to a "u" but wanted to log this as a bug for future patches consideration.

[seanshankus]

(28-12-2022 17:00)seanshankus Wrote:  Directly after i updated to 2.2, i'm not getting the following error:
Unexpected exception java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: Vince Guaraldi Trio/A Charlie Brown Christmas/1.10 - Für Elise.flac

I was not getting this in 2.1.2. I suspect it doesn't like "ü" and can change that to a "u" but wanted to log this as a bug for future patches consideration.

I think this might be at a lower linux level. I updated the kernel recently and suspect this is the root issue and not Mimimserver update.....

[simoncn]

Please post the full Java stack trace for this InvalidPathException. You can find this in the minimserver.log file. Many thanks.

[seanshankus]

okay just for completness, the issue was not Miminserver at all, it just "appeared" after i updated so complete coincidence. The issue, which i still don't understand "how" was that my default locale was changed. i have two minimservers each in their own LXC containers and setup the same. neither my host server or the other container had this issue, which allowed me to to compare and ultimately figure out that the linux locales were different.

The fix was to uncomment in the en_US.UTF-8 UTF-8 line (again not sure what or how it was commented out in the first place), rerun dpkg-reconfigure locales, selecting the en_US.UTF-8 and reboot. MinimServer then scanned the directories just fine like it did a few weeks ago.

[Exiled]

I have the same problem. After upgrading from 2.1.2 update 222 to 2.2 update 231, MinimServer fails to start and the log file shows the above error with reference to a file containing an accented character. I tried re-naming that file to eliminate the accent, and MinimServer now fails on the next file with accents in the file name.

In my case I have not changed locale or character set info. The MinimServer log contains the following both before and after the upgrade: "Platform default charset is US-ASCII".

MinimServer is running on Synology DSM 4.2. I've found a procedure to update system locale/char set on the NAS, but I'm not sure if it will have an impact on other applications so I'd prefer not to if there's an easier way around this problem.

Stack trace:
java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: Rameau, Jean-Philippe/Les Grands Motets (1994)/03 In convertendo - 3 Lent - très gai 'Magnificavit Dominus'.flac
at java.base/sun.nio.fs.UnixPath.encode(UnixPath.java:145)
at java.base/sun.nio.fs.UnixPath.<init>(UnixPath.java:69)
at java.base/sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:279)
at java.base/java.nio.file.Path.resolve(Path.java:515)
at com.minimserver.Server$CachedAudioItem.getItemAbsolutePath(Server.java:20421)
at com.minimserver.Server.processAudioItem(Server.java:9747)
at com.minimserver.Server.access$15500(Server.java:185)
at com.minimserver.Server$Directory.postVisit(Server.java:17542)
at com.minimserver.Server$Visitor.postVisitDirectory(Server.java:17944)
at com.minimserver.Server$Visitor.postVisitDirectory(Server.java:17807)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2822)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2876)
at com.minimserver.Server.readFiles(Server.java:8718)
at com.minimserver.Server.doStart(Server.java:3826)
at com.minimserver.Server.start(Server.java:1400)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:240)
at org.jminim.core.ContextImpl.start(ContextImpl.java:128)
at org.jminim.core.RootContextImpl.startComponent(RootContextImpl.java:80)
at org.jminim.core.ContextImpl.start(ContextImpl.java:128)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2796)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1317)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:125)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.jminim.mlaunch.MinimLaunch.doLaunch(MinimLaunch.java:525)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:150)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:90)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.jminim.launch.Launcher.launch(Launcher.java:88)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:38)

[simoncn]

Thanks for posting the stack trace. From this, I can see what is causing the problem. The fix should not be too difficult and I hope to be able to release an update with this fix some time later today.

[simoncn]

PM sent.

[simoncn]

This problem is fixed in MinimServer update 235.

[Exiled]

Thanks, Simon!