[GH-ISSUE #86] [Bug]: Starting print for queue fails every time #42

Closed
opened 2026-05-06 12:25:09 +02:00 by BreizhHardware · 5 comments

Originally created by @pinionless on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/86

Originally assigned to: @maziggy on GitHub.

Bug Description

Every time I tried to release a print waiting in a queue - it failed. (printing from archive works)

One time with error: "Failed to send print command" in Bambuddy
And all other times I got the: "MicroSD Card read/write exception error" on my printer.

The logs should show attempt to start the print, first from queue and later from archive.
Starting print from archive works like expected.

bambuddy-support-20260114-170225.zip

Expected Behavior

Print starts successfully

Steps to Reproduce

  1. Schedule a print that is in the archives in the "Queue Only" mode
  2. Go to Queue and release the print
  3. ERROR

Printer Model

A1

Bambuddy Version

v0.1.6b7

Printer Firmware Version

v1.07

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs


Screenshots

No response

Additional Context

  • My SD Card is not corrupted, after few failed prints I just upgraded to samsung max endurance
  • Bambuddy thinks that print was successfully started when SD Card error is displayed
  • Sometimes instead of sd card error there was a "failed to print error". I could not reproduce it during debug logs recording.
  • I was never able to start a print from queue, started multiple from archive.

Checklist

  • I have searched existing issues to ensure this bug hasn't already been reported
  • I am using the latest version of Bambuddy
  • My printer is set to LAN Only mode
Originally created by @pinionless on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/86 Originally assigned to: @maziggy on GitHub. ### Bug Description Every time I tried to release a print waiting in a queue - it failed. (printing from archive works) One time with error: "Failed to send print command" in Bambuddy And all other times I got the: "MicroSD Card read/write exception error" on my printer. The logs should show attempt to start the print, first from queue and later from archive. Starting print from archive works like expected. [bambuddy-support-20260114-170225.zip](https://github.com/user-attachments/files/24618368/bambuddy-support-20260114-170225.zip) ### Expected Behavior Print starts successfully ### Steps to Reproduce 1. Schedule a print that is in the archives in the "Queue Only" mode 2. Go to Queue and release the print 3. ERROR ### Printer Model A1 ### Bambuddy Version v0.1.6b7 ### Printer Firmware Version v1.07 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs ```shell ``` ### Screenshots _No response_ ### Additional Context - My SD Card is not corrupted, after few failed prints I just upgraded to samsung max endurance - Bambuddy thinks that print was successfully started when SD Card error is displayed - Sometimes instead of sd card error there was a "failed to print error". I could not reproduce it during debug logs recording. - I was never able to start a print from queue, started multiple from archive. ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [ ] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode
BreizhHardware 2026-05-06 12:25:09 +02:00
Author
Owner

@maziggy commented on GitHub (Jan 14, 2026):

Please first update to branch 0.1.6b8. It inlcudes multiple A1 related fixes.

<!-- gh-comment-id:3750360506 --> @maziggy commented on GitHub (Jan 14, 2026): Please first update to branch 0.1.6b8. It inlcudes multiple A1 related fixes.
Author
Owner

@pinionless commented on GitHub (Jan 14, 2026):

OK. I will test again tomorrow on the new version

<!-- gh-comment-id:3750382997 --> @pinionless commented on GitHub (Jan 14, 2026): OK. I will test again tomorrow on the new version
Author
Owner

@pinionless commented on GitHub (Jan 15, 2026):

Just run a test on 0.1.6b8

  1. add print from archive to queue
  2. release from queue
  3. SD card error in the printer
  4. Exit error on printer
  5. press finish print on printer
  6. delete print from queue - Bambuddy thinks it started successfully

  1. delete file from printer (it uploaded to /cache during queue test)
  2. start print from archive
  3. print starts without issues.

Observed exactly this same behavior as on last version

There must be some difference in how prints are started manually and from queue.

Logs from this test.
bambuddy-support-20260115-221709.zip

<!-- gh-comment-id:3756922776 --> @pinionless commented on GitHub (Jan 15, 2026): Just run a test on 0.1.6b8 1. add print from archive to queue 2. release from queue 3. SD card error in the printer 4. Exit error on printer 5. press finish print on printer 6. delete print from queue - Bambuddy thinks it started successfully --- 7. delete file from printer (it uploaded to /cache during queue test) 8. start print from archive 9. print starts without issues. Observed exactly this same behavior as on last version There must be some difference in how prints are started manually and from queue. Logs from this test. [bambuddy-support-20260115-221709.zip](https://github.com/user-attachments/files/24652926/bambuddy-support-20260115-221709.zip)
Author
Owner

@maziggy commented on GitHub (Jan 16, 2026):

The problem was a non matching file path. Should now be fixed. PLease use branch 0.1.6b8 and let me know if it works now.

<!-- gh-comment-id:3758419178 --> @maziggy commented on GitHub (Jan 16, 2026): The problem was a non matching file path. Should now be fixed. PLease use branch 0.1.6b8 and let me know if it works now.
Author
Owner

@pinionless commented on GitHub (Jan 18, 2026):

Tested with a single print.

Works for me.

<!-- gh-comment-id:3765502816 --> @pinionless commented on GitHub (Jan 18, 2026): Tested with a single print. Works for me.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#42
No description provided.