[GH-ISSUE #927] [Bug]: Synchronizing device information times out in Orca when using virtual printer #640

Closed
opened 2026-05-06 12:31:35 +02:00 by BreizhHardware · 12 comments

Originally created by @EdwardChamberlain on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/927

Originally assigned to: @maziggy on GitHub.

Bug Description

Synchronizing device information times out in Orca when using the virtual printer. It seems that bambuddy is not responding in the way that orca requires causing it to time out. This causes a delay in being able to send the job.

Expected Behavior

Device info synced.

Steps to Reproduce

1 - Slice model
2 - Click Send
3 - Screen hangs on "Synchronizing device information..." before moving to "Synchronizing device information timed out."
4 - Send job anyway

Printer Model

Not printer-related

Bambuddy Version

v0.2.3b2 & v.0.2.2

Printer Firmware Version

01.10.00.00

Installation Method

Docker

Operating System

Linux (Other)

Relevant Logs / Support Package

bambuddy-support-20260409-192648.zip

Screenshots

Image Image Image

Additional Context

This also causes orca to crash (I think unrelated to bambuddy)

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
  • My printer has Developer Mode enabled
Originally created by @EdwardChamberlain on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/927 Originally assigned to: @maziggy on GitHub. ### Bug Description Synchronizing device information times out in Orca when using the virtual printer. It seems that bambuddy is not responding in the way that orca requires causing it to time out. This causes a delay in being able to send the job. ### Expected Behavior Device info synced. ### Steps to Reproduce 1 - Slice model 2 - Click Send 3 - Screen hangs on "Synchronizing device information..." before moving to "Synchronizing device information timed out." 4 - Send job anyway ### Printer Model Not printer-related ### Bambuddy Version v0.2.3b2 & v.0.2.2 ### Printer Firmware Version 01.10.00.00 ### Installation Method Docker ### Operating System Linux (Other) ### Relevant Logs / Support Package [bambuddy-support-20260409-192648.zip](https://github.com/user-attachments/files/26612135/bambuddy-support-20260409-192648.zip) ### Screenshots <img width="480" height="291" alt="Image" src="https://github.com/user-attachments/assets/98462093-845c-4062-84fc-daaf3c0419e0" /> <img width="483" height="281" alt="Image" src="https://github.com/user-attachments/assets/87ea5d54-f3ff-4e19-a7c1-bbb64f57c127" /> <img width="1112" height="912" alt="Image" src="https://github.com/user-attachments/assets/16a685c2-910f-41e7-aca4-4be018f89eec" /> ### Additional Context This also causes orca to crash (I think unrelated to bambuddy) ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled
BreizhHardware 2026-05-06 12:31:35 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@maziggy commented on GitHub (Apr 9, 2026):

Debug logging was started after connecting to the proxy. Please first enable debug logging, then connect your slicer to the proxy and send the file.

<!-- gh-comment-id:4216564293 --> @maziggy commented on GitHub (Apr 9, 2026): Debug logging was started after connecting to the proxy. Please first enable debug logging, then connect your slicer to the proxy and send the file.
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 9, 2026):

bambuddy-support-20260409-200554.zip

Enable debug logging -> open orca slicer -> Slice -> Send job -> download support file

<!-- gh-comment-id:4216810016 --> @EdwardChamberlain commented on GitHub (Apr 9, 2026): [bambuddy-support-20260409-200554.zip](https://github.com/user-attachments/files/26612884/bambuddy-support-20260409-200554.zip) Enable debug logging -> open orca slicer -> Slice -> Send job -> download support file
Author
Owner

@maziggy commented on GitHub (Apr 10, 2026):

You don't have a target printer selected for your virtual printer.

"virtual_printers": [
{
"index": 1,
"enabled": true,
"mode": "print_queue",
"model": "C12",
"model_name": "P1S",
"has_target_printer": false,
"has_bind_ip": true,
"running": true,
"pending_files": 0
}

<!-- gh-comment-id:4222085757 --> @maziggy commented on GitHub (Apr 10, 2026): You don't have a target printer selected for your virtual printer. "virtual_printers": [ { "index": 1, "enabled": true, "mode": "print_queue", "model": "C12", "model_name": "P1S", **"has_target_printer": false,** "has_bind_ip": true, "running": true, "pending_files": 0 }
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 10, 2026):

I have added a target printer and repeated the steps but still get the same error:

Image

bambuddy-support-20260410-090452.zip

<!-- gh-comment-id:4222111236 --> @EdwardChamberlain commented on GitHub (Apr 10, 2026): I have added a target printer and repeated the steps but still get the same error: <img width="506" height="316" alt="Image" src="https://github.com/user-attachments/assets/3164016a-92bf-4657-b415-acd09b593767" /> [bambuddy-support-20260410-090452.zip](https://github.com/user-attachments/files/26624103/bambuddy-support-20260410-090452.zip)
Author
Owner

@maziggy commented on GitHub (Apr 10, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:4222783153 --> @maziggy commented on GitHub (Apr 10, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 10, 2026):

Im running in docker on :daily so will grab the next daily build when it is ready (looks like the last daily is currently 23 hours old so should see one soon)

<!-- gh-comment-id:4222988885 --> @EdwardChamberlain commented on GitHub (Apr 10, 2026): Im running in docker on :daily so will grab the next daily build when it is ready (looks like the last daily is currently 23 hours old so should see one soon)
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 10, 2026):

Now running latest daily (1 hour ago). Issue is still present
"ghcr.io/maziggy/bambuddy@sha256:3236a5d9052ea5fe7ce49d2bc7e0fcd0cbca980acd068a3985cfe15d3c9bbaba"

bambuddy-support-20260410-185855.zip

<!-- gh-comment-id:4225769340 --> @EdwardChamberlain commented on GitHub (Apr 10, 2026): Now running latest daily (1 hour ago). Issue is still present "ghcr.io/maziggy/bambuddy@sha256:3236a5d9052ea5fe7ce49d2bc7e0fcd0cbca980acd068a3985cfe15d3c9bbaba" [bambuddy-support-20260410-185855.zip](https://github.com/user-attachments/files/26637198/bambuddy-support-20260410-185855.zip)
Author
Owner

@maziggy commented on GitHub (Apr 11, 2026):

Just tested with all my printers and cannot reproduce the problem. There must be something wrong with your system.

Please show me a screenshot of your virtual printer settings.

<!-- gh-comment-id:4229115896 --> @maziggy commented on GitHub (Apr 11, 2026): Just tested with all my printers and cannot reproduce the problem. There must be something wrong with your system. Please show me a screenshot of your virtual printer settings.
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 13, 2026):

Settings as follows:

image

<!-- gh-comment-id:4236419256 --> @EdwardChamberlain commented on GitHub (Apr 13, 2026): Settings as follows: ![image](https://github.com/user-attachments/assets/927934d5-3dae-492f-9348-1b6fa6a187ba)
Author
Owner

@maziggy commented on GitHub (Apr 13, 2026):

Hmmm....looks good. What happens if you try exactly the same with your other printer?

<!-- gh-comment-id:4236497537 --> @maziggy commented on GitHub (Apr 13, 2026): Hmmm....looks good. What happens if you try exactly the same with your other printer?
Author
Owner

@EdwardChamberlain commented on GitHub (Apr 18, 2026):

Switching target printer to my other P1S causes the same issue. Same issue if I switch model to H2S and point it to my H2S - orca never syncs.

I can sync with the printer if I select the LAN printer via the orca window, it's only the virtual printer that shows this issue.

<!-- gh-comment-id:4273961671 --> @EdwardChamberlain commented on GitHub (Apr 18, 2026): Switching target printer to my other P1S causes the same issue. Same issue if I switch model to H2S and point it to my H2S - orca never syncs. I can sync with the printer if I select the LAN printer via the orca window, it's only the virtual printer that shows this issue.
Author
Owner

@maziggy commented on GitHub (Apr 19, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if to works for you now.


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:4275302229 --> @maziggy commented on GitHub (Apr 19, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if to works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
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#640
No description provided.