mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #550] [Bug]: camara button still works even tho it is turned off in the premisions #358
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#358
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 @Minebuddy on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/550
Originally assigned to: @maziggy on GitHub.
Bug Description
The camera button does not disable (gray out) when camera permissions are turned off.
Additionally, the ffmpeg process does not terminate properly and remains active after closing steam. Each camera stream consumes approximately 240MB of memory per ffmpeg instance.
With 6 printers in operation and multiple students accessing streams, this results in significant memory usage.
Expected Behavior
The camera button should automatically gray out (be disabled) when camera permissions are turned off.
The ffmpeg process should properly terminate once a camera stream is closed, ensuring no lingering processes remain and no unnecessary memory continues to be consumed.
Steps to Reproduce
Printer Model
P2S
Bambuddy Version
v0.2.1
Printer Firmware Version
01.01.03.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 28, 2026):
Yeah, already have the ffmpeg processes on my list. Anyway, let me check.
@Minebuddy commented on GitHub (Feb 28, 2026):
Got it.
I have one more thing: (sorry for not making another post for this)
The sidebar menu currently shows tabs even if they are completely disabled via permissions. It would be better if tabs that are disabled in permissions simply did not appear at all.
Right now, I get a lot of questions about why certain sections don’t work, and I have to repeatedly explain that they’re disabled in the permissions.
For my use case, I only need student to have access to:
However, all tabs are visible at the moment, which isn’t ideal.
@maziggy commented on GitHub (Feb 28, 2026):
Fixed in branch 0.2.2b1.
Ffmpeg processes are now cleaned up every 60 seconds, if window was closed and process is still running.
Regarding the sidebar navigation not respecting user's permissons: this si also fixed in branch 0.2.2b1 :)
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!
@Minebuddy commented on GitHub (Feb 28, 2026):
the new branch is not show in releases for me
@maziggy commented on GitHub (Feb 28, 2026):
Because it is not released :)
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
@Minebuddy commented on GitHub (Feb 28, 2026):
i use portainer.io so what you just told me i have no clue what that all means if it is something i have to do in the editor i can do this if i have to go into command line this is not someting i can do
@maziggy commented on GitHub (Feb 28, 2026):
Don't think that you can do it via Portainer. It only supports pulling images, but not rebuilding images from source. I'm sorry.
@Minebuddy commented on GitHub (Feb 28, 2026):
It’s a bit unfortunate I’d really love to test the fix, but I can only do that if there’s a new release that includes it.
I don’t fully trust myself to update it manually through the command line. I’m not a supper advanced user, and I don’t want to risk breaking the setup. It already took me quite some time to get everything configured the way I want it.
On top of that, this is a live environment that’s actively being used, so I have to be careful with changes.
@maziggy commented on GitHub (Feb 28, 2026):
In this case you have to wait for the next release. I'm sorry.
@Minebuddy commented on GitHub (Feb 28, 2026):
I appreciate the help either way. I’ll wait for the official fix and I’m happy to test it once it’s released. Thanks again for the quick turnaround on the bug fixes.