Basic Information: I’m reporting this for some of my users who are having problems printing some files based on the file name. It appears to be a broad klipper issue, not focused on a specific printer. Describe your issue: Klipper gets angry about files with # in the name of the gcode. # is a leg…

I recognize this is almost certainly being parsed as a comment, so my hope here is that klipper would at least recognize that the file name will break, and do a character replace on the # or error.

This is a general problem with the parsing of extended g-code commands, not specific to filename handling. One way to avoid it is to use standard codes (e.g. M23) instead.

[image] devonjones: # is a legit character on windows, mac and linux for a filename. While this might be true, I guess everyone old enough to know what a traditional 8.3 filename is gets cold shivers just thinking about it. Not everything that is legitimate needs to be used. Nuclear weapons a…

Note that this should have been fixed by gcode: Improve handling of extended g-code commands with '*;#' charac… · Klipper3d/klipper@d45b9c9 · GitHub , so anyone still reporting it is probably running an outdated version. If not, an actual bug report including the information requested by the standard…

[image] flowerysong: so anyone still reporting it is probably running an outdated version It’s hard to say, because the OP ignored/deleted the template and posted no klippy.log.

I’ll see what I can get. I run an stl patreon, and it’s from one of my patrons.

Hard to fill out the template when it’s a bug for a printer that isn’t yours. I get the frustration, I’m in tech as well, but all I had from them was the screenshot I posted

Unfortunately, further follow-up is only possible with the log showing the issue. As mentioned by @flowerysong , the bug might already be fixed, and all the user needs to do is update their Klipper version.

Latest from them is this: Hi guys. My version was v1.2.3.1. I hadn’t thought to do another update, so apologies for that. I updated to 1.2.3.4 and the current UI as well. Files with # still not working. Printer freezes at the “preparing to print” screen and another console error. I’ve requested hi…

@devonjones [image] Sineos: Unfortunately, further follow-up is only possible with the log showing the issue. Why don’t you post your klippy.log?

Klipper fails on files with # in the name

General Discussion

3dcoded May 21, 2025, 11:35pm 18

Maybe this will explain why the help we can offer for this printer will be pretty limited.

Topic		Replies	Views
Please check possible error/feature General Discussion	5	3164	October 17, 2022
Klipper crashes on unhandled exception when starting print General Discussion	2	166	February 17, 2024
Print error at start General Discussion	2	1915	October 3, 2023
Klipper crashes when Exclude_Object_Define contains non-ascii characters General Discussion	2	1395	January 22, 2023
Bug with Cyrillic in gcode comments General Discussion	7	302	March 4, 2024

Klipper fails on files with # in the name

Related topics