mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #558] [Bug]: queue empty with 500 error #364
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
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#364
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 @Dendrowen on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/558
Originally assigned to: @maziggy on GitHub.
Bug Description
Queue list suddenly not showing items unless filtering on state. It worked before but after some fiddling with canceling a print and reordering the queue it disappeared entirely unless I filter on a state like 'pending'.
Expected Behavior
When opening the queue I should see all the items in the queue in every possible state when the 'All states' option is selected.
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.2.1.1
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@Dendrowen commented on GitHub (Feb 28, 2026):
bambuddy-support-20260228-222534.zip
@Dendrowen commented on GitHub (Feb 28, 2026):
the request is getting 500 errors. Also when calling the api from home assistant.
My thought was that a queue item moght've gotten corrupted somehow, but all the status filters seem to be working.
@maziggy commented on GitHub (Mar 1, 2026):
Permission problem.
2026-02-28 11:19:59,797 ERROR [backend.app.services.virtual_printer.manager] Cannot create directory /app/data/virtual_printer/uploads: 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'
@maziggy commented on GitHub (Mar 1, 2026):
Cannot reproduce the problem, but I guess it's triggered by failed/aborted prints.
Please use branch 0.2.2b1 and let me know how it goes.
@Dendrowen commented on GitHub (Mar 1, 2026):
I am on docker. How do I use 0.2.2b1? I can't see it on https://github.com/maziggy/bambuddy/pkgs/container/bambuddy
fixing the permissions did not resolve the problem
@maziggy commented on GitHub (Mar 1, 2026):
cd to your bambuddy folder and do a
git pull && git checkout 0.2.2b1 && git pull && docker compose down && docker compose up --build -d
@Percy2Live commented on GitHub (Mar 1, 2026):
This isn't working for standard users. @Dendrowen just wait for a tagged version, I also wait to verify a fix in 0.2.2b1
This looks similar to my bug in #523, you may want to check if the problem persists if you stop the container, remove the WAL and SHM file and restart it (backup recommended).
@maziggy commented on GitHub (Mar 1, 2026):
Why do you think rebuilding an image is not working?
@Percy2Live commented on GitHub (Mar 1, 2026):
99% of the standard users use an environment without git being installed. For productive environments I have no need for git as well - and even if I would like to install this, it's not working on all systems. E.g. I'm running DSM from Synology on the system I deploy bambuddy, rebuilding the image on this system is not trivial and it's not sufficient to run the command you posted. Hence I rely on tagged versions to test the latest builds. To make this clear: I don't want to criticize you for not publishing a tagged version, I just noticed you receive the same question over and over again in a lot of bug reports by the authors - I believe most of them are non-devs, so this is probably the explanation. Consider making the latest builds more accessible for your non-developer community by releasing tagged versions for betas and maybe even alphas (I already noticed a lot of improvement here, thanks!)
@maziggy commented on GitHub (Mar 1, 2026):
Very helpful feedback!
I could think of publishing nightly builds. That should help, right?
@Percy2Live commented on GitHub (Mar 1, 2026):
Sure, that would help!
@maziggy commented on GitHub (Mar 1, 2026):
Done!
@Dendrowen commented on GitHub (Mar 1, 2026):
0.2.2b1 fixed the issue. I now have two prints running simultaneously on a single printer according to bambuddy, but I would think that ought to clear up when it's done.