starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #1106] [Bug]: Camera on my x1c does not open it shows white screen after todays daily update. #791

New issue

Closed

opened 2026-05-06 12:32:56 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-06 12:32:56 +02:00

Owner

Originally created by @TheMrCaveman on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1106

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

As soon as I open the camera feed in bambuddy it opens: http://192.168.1.224:8000/camera/1 and shows a white screen.

Expected Behavior

Normally it would show me my camera feed.
Edit 21:12 If I keep trying it sometimes opens the camera feed as it should.

Steps to Reproduce

open Bambuddy
Got to printer tab
open camera feed.

Printer Model

X1 Carbon

Bambuddy Version

v0.2.4b1

SpoolBuddy Version

No response

Printer Firmware Version

01.11.02.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

bambuddy-support-20260423-204454.zip

Screenshots

Additional Context

No response

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 @TheMrCaveman on GitHub (Apr 23, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1106 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description As soon as I open the camera feed in bambuddy it opens: http://192.168.1.224:8000/camera/1 and shows a white screen. ### Expected Behavior Normally it would show me my camera feed. Edit 21:12 If I keep trying it sometimes opens the camera feed as it should. ### Steps to Reproduce open Bambuddy Got to printer tab open camera feed. ### Printer Model X1 Carbon ### Bambuddy Version v0.2.4b1 ### SpoolBuddy Version _No response_ ### Printer Firmware Version 01.11.02.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package [bambuddy-support-20260423-204454.zip](https://github.com/user-attachments/files/27022725/bambuddy-support-20260423-204454.zip) ### Screenshots <img width="1909" height="1148" alt="Image" src="https://github.com/user-attachments/assets/d6eb8293-82f0-4173-b7c2-8671d5267076" /> ### Additional Context _No response_ ### 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:32:56 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:32:57 +02:00

Author

Owner

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

2026-04-17 16:11:25,710 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/uploads: Permission denied. For Docker: ensure t
he data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer'
2026-04-17 16:11:25,711 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/certs: Permission denied. For Docker: ensure the
data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer'
2026-04-17 16:21:02,005 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/uploads: Permission denied. For Docker: ensure t
he data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer'
2026-04-17 16:21:02,006 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/certs: Permission denied. For Docker: ensure the
data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer'
2026-04-17 16:26:34,200 ERROR [backend.app.api.routes.virtual_printers] Failed to sync virtual printers after update: [Errno 13] Permission denied: '/app/data/virtual_printer/
uploads'

Fix your permissions!

@maziggy commented on GitHub (Apr 24, 2026): > 2026-04-17 16:11:25,710 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/uploads: Permission denied. For Docker: ensure t he data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer' > 2026-04-17 16:11:25,711 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/certs: Permission denied. For Docker: ensure the data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer' > 2026-04-17 16:21:02,005 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/uploads: Permission denied. For Docker: ensure t he data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer' > 2026-04-17 16:21:02,006 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/certs: Permission denied. For Docker: ensure the data volume is writable by the container user. For bare metal: run 'sudo chown -R $(whoami) /app/data/virtual_printer' > 2026-04-17 16:26:34,200 ERROR [backend.app.api.routes.virtual_printers] Failed to sync virtual printers after update: [Errno 13] Permission denied: '/app/data/virtual_printer/ uploads' Fix your permissions!

BreizhHardware commented

2026-05-06 12:32:57 +02:00

Author

Owner

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

I also have a X1C with same firmware version and cannot reproduce the issue — when I open the camera on mine the log shows exactly one Starting RTSP camera stream line per open. Yours shows the frontend firing two ffmpeg spawns 140 ms apart on every camera open (e.g. 16:15:09,571 + 16:15:09,707, again at 16:35:46,180 +16:35:46,325). X1C only supports one concurrent RTSPS session, so the second spawn kicks the first — that's the white screen. Retrying eventually works because by then
only one session wins.

To narrow down what's triggering the double-spawn on your setup, can you check:

Is your HomeAssistant integration configured with a camera entity pointed at Bambuddy or directly at the X1C? If yes, try disabling it temporarily and see if the white screen goes away.
Settings → Camera view mode — is it on Window (popup) or Embedded? If it's Window, try switching to Embedded and see if the behaviour changes.
Have you opened the Bambuddy UI in more than one browser tab at the same time? Each open tab subscribes to the same camera endpoint.
Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything? Wondering if a stale JS bundle from before today's update is still running.

Not a fix yet — just trying to find which of those is triggering it, because your working X1C on my side and your broken X1C on yours is the clearest difference.

@maziggy commented on GitHub (Apr 24, 2026): I also have a X1C with same firmware version and cannot reproduce the issue — when I open the camera on mine the log shows exactly one Starting RTSP camera stream line per open. Yours shows the frontend firing two ffmpeg spawns 140 ms apart on every camera open (e.g. 16:15:09,571 + 16:15:09,707, again at 16:35:46,180 +16:35:46,325). X1C only supports one concurrent RTSPS session, so the second spawn kicks the first — that's the white screen. Retrying eventually works because by then only one session wins. To narrow down what's triggering the double-spawn on your setup, can you check: 1. Is your HomeAssistant integration configured with a camera entity pointed at Bambuddy or directly at the X1C? If yes, try disabling it temporarily and see if the white screen goes away. 2. Settings → Camera view mode — is it on Window (popup) or Embedded? If it's Window, try switching to Embedded and see if the behaviour changes. 3. Have you opened the Bambuddy UI in more than one browser tab at the same time? Each open tab subscribes to the same camera endpoint. 4. Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything? Wondering if a stale JS bundle from before today's update is still running. Not a fix yet — just trying to find which of those is triggering it, because your working X1C on my side and your broken X1C on yours is the clearest difference.

BreizhHardware commented

2026-05-06 12:32:57 +02:00

Author

Owner

@TheMrCaveman commented on GitHub (Apr 24, 2026):

Tried to replicate it today. And cannot replicate it in any way i could yesterday.

Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything? Wondering if a stale JS bundle from before today's update is still running.

Only difference between yesterday and today is a rebooted pc.

@TheMrCaveman commented on GitHub (Apr 24, 2026): Tried to replicate it today. And cannot replicate it in any way i could yesterday. Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything? Wondering if a stale JS bundle from before today's update is still running. Only difference between yesterday and today is a rebooted pc.

BreizhHardware commented

2026-05-06 12:32:58 +02:00

Author

Owner

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

Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything?

Yes! Golden rule: something is odd? Froce reload page (Shift+Reload).

Will close the issue. Let me know if you have any issues again.

@maziggy commented on GitHub (Apr 25, 2026): > Does a hard browser cache clear (Shift+F5, or clear site data for Bambuddy's origin) change anything? Yes! Golden rule: something is odd? Froce reload page (Shift+Reload). Will close the issue. Let me know if you have any issues again.

BreizhHardware referenced this issue

2026-05-06 12:35:21 +02:00

[PR #1029] [MERGED] v0.2.3 final #1149