mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #252] [Bug]: Archive files do not show pictures & can not connect with 3mf file #156
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#156
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 @BenGeba on GitHub (Feb 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/252
Originally assigned to: @maziggy on GitHub.
Bug Description
When I am in the Archive section and want to assign a .3mf to a GCODE file, I get an error. Images are also not displayed even though they are available.
Expected Behavior
I can see the attached images and link the .3mf files.
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.1.7
Printer Firmware Version
01.09
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
According to the logs, it saves the file under /app/source/.
However, Bambuddy expects the path to be under settings.base_dir = /app/data and then does:
source_path.relative_to(settings.base_dir)
→ crashes because /app/source/... is not under /app/data/...
Checklist
@BenGeba commented on GitHub (Feb 3, 2026):
Also seems to be related to the error https://github.com/maziggy/bambuddy/issues/232
@maziggy commented on GitHub (Feb 3, 2026):
Did you restart the container after upgrading? To me it looks like the database migration was not done.
@BenGeba commented on GitHub (Feb 3, 2026):
It was a fresh install from docker compose
@maziggy commented on GitHub (Feb 3, 2026):
Just to make sure, please rebuild the image.
@BenGeba commented on GitHub (Feb 3, 2026):
Apparently, there was an error caused by Komodo (a Portainer alternative). I removed and deleted the container from the compose there and added it again using the installation script. Now it works. But I wonder why there were errors with Komodo?
@andretietz commented on GitHub (Feb 3, 2026):
Good that you mention that. I am having the same problem using the P2S. But I am running on the prebuild images from github. @BenGeba did you try if the prebuild one for you has the same problem?
If so, the image build has an issue somehow.
@maziggy commented on GitHub (Feb 4, 2026):
Sorry, I don't know Komodo at all.
@andretietz commented on GitHub (Feb 4, 2026):
@maziggy
If the pre built images from bambuddy (the ones you provide) are broken as well, this is not related to komodo.
Please verify at least, that the prebuild images work as intended, they don't work for me though
@maziggy commented on GitHub (Feb 4, 2026):
The images are not broken. As already said it looks like a migration task was not triggered when you upgraded your installation. I can only suggest to do a clean install and watch the logs for errors.