mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #174] [Bug]: Cannot send print job to printer #114
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#114
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tropaion on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/174
Originally assigned to: @maziggy on GitHub.
Bug Description
Hello,
I managed to get everything to work now except that I can't send a print job to the printer.
I always get the error: "Failed to upload file to printer"
Expected Behavior
Printer starts printing
Steps to Reproduce
Printer Model
X1 Carbon
Bambuddy Version
v0.1.6b11
Printer Firmware Version
01.11.02.00
Installation Method
Manual (git clone)
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Jan 29, 2026):
Please use branch 0.1.6-final and create a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@Tropaion commented on GitHub (Jan 29, 2026):
Done, here is the support package:
bambuddy-support-20260129-134752.zip
@maziggy commented on GitHub (Jan 29, 2026):
Do you have a SD card in the printer?
@eliezedeck commented on GitHub (Jan 29, 2026):
I think I also have an issue printing. I have a P1P and an X1C. Both don't print.
I already recompiled the Docker image for 0.1.6-final ... it behaved exactly as 0.1.6-b11 that was from latest I checked-out earlier.
What's also interesting, is that if I use the queue to start the print, it will return a "Archive not found" error instead. Printing from File manager will just hang, and after some time, the dialog can be closed. No error message visible.
@maziggy commented on GitHub (Jan 29, 2026):
Again: do you have a SD card in the printer?
@eliezedeck commented on GitHub (Jan 29, 2026):
For my case, I do have a microSD inside the printer. What's really strange, is that with 0.1.6-final, at first it didn't succeed. Then I kind of just gave up. After about 20 minutes, it started printing! I mean, what?! it failed or it succeeded?
The way I see it is that there are some sort of retries that goes on forever. I think that's problematic. If it failed, it should fail fast and just stop.
Also, just a question: wouldn't it be more interesting to have the option to command the printer to print files ALREADY on the microSD instead of always uploading to the printer?
@maziggy commented on GitHub (Jan 29, 2026):
Is there enough free space on the SD card?
Anyway....i added some additional debug logging. Please use branch test/issue_174 and send me a new suppport package. Then we should see what's happening when uploading the file to the printer.
@Tropaion commented on GitHub (Jan 29, 2026):
@maziggy in my case you were right, I had no sd card. Didn't know it was nessesary. Not it works.
@eliezedeck commented on GitHub (Jan 30, 2026):
@maziggy while I'll be testing the test/issue_174 somewhere in the weekends... I have left the Docker running (as I also plan to do). Bad surprise: it cause the previous past print command to print unattended, no queues involved here. There is definitely some endless retry here, and when it succeeds, it will cause the printer to start printing randomly. This is a critical behavior issue.
Fortunately, there was not left-over print on the bed, and that the filament was still plenty. But still, bad surprise.
@maziggy commented on GitHub (Jan 30, 2026):
@eliezedeck: please send me the logs!!!
@opensourcefan commented on GitHub (Feb 2, 2026):
I'm having the same issue. I've completely wiped it from my docker instance (including volumes) and reinstalled, no change. Manually added my printer, no change. Formatted sd care, no change, Printer installs just fine, and files on sd card are visible but I also get a sd card failure. Upload works fine via Orca Slicer.
I have also experienced the random print starts as well.
Edit: This occurs on the 7b update as well.
@opensourcefan commented on GitHub (Feb 2, 2026):
`2026-02-02 06:45:14,688 INFO [backend.app.services.bambu_ftp] FTP storage diagnostics: can_list_root=False, can_list_cache=False, storage={'used_bytes': 0}, errors=['LIST / failed: ', 'LIST /cache failed: ']
2026-02-02 06:45:14,690 ERROR [backend.app.services.bambu_ftp] FTP upload failed for /14_Motor_Mount_PLA_1h32m.3mf: (type: EOFError)
`
If I go to Files in the printer on the Printers page it access and shows the sd card files no problem.
@maziggy commented on GitHub (Feb 2, 2026):
Please first update to the latest version and send a new support package.
@YoungReckless4 commented on GitHub (Feb 2, 2026):
@maziggy Hi.
I'm have same EOFError.
bambuddy-support-20260202-231439.zip
@maziggy commented on GitHub (Feb 3, 2026):
@YoungReckless4 This ticket is for a X1C, you have an A1. Please open a separate issue. Thanks.
@maziggy commented on GitHub (Feb 3, 2026):
@Tropaion I'm confused now due to the mix up of different printer models in this issue.
So this issue is for the X1C. Please use branch 0.1.7b and send me a new support package.
@opensourcefan commented on GitHub (Feb 3, 2026):
A1 Mini for me.
@maziggy commented on GitHub (Feb 3, 2026):
@opensourcefan please open a separate ticket. I'm losing the overview when a ticket deals with different printer models.