mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #981] [Bug Report] Printing jobs not shown in Queue view #684
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
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-maziggy-1#684
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 @maziggy on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/981
Originally assigned to: @maziggy on GitHub.
Printing jobs not shown in Queue view
Screenshot
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@tom5677 commented on GitHub (Apr 14, 2026):
Now the same thing happened like in issue #978 : no print, but the job, which was not printed is now showng as 100% in "currently printing" section. Thanks for your help!
@tom5677 commented on GitHub (Apr 14, 2026):
now I did some testing regarding the specific behaviour above. It only happens when sending a file via "Schedule" > ASAP from the file manager (and then confirm empty plate). It takes some time (assume the upload in the background), then the additional entry appears with 100%
...
THen after deleting/stopping those 100%-printing entries (=stop printing), and then sending the same file again it worked.
BUT: all 3 printers are printing (and showing the files in the printer view), but NOT in the queue view under "currently printed"
Thanks!
@tom5677 commented on GitHub (Apr 15, 2026):
Maybe it's an issue on my side regarding IP addesses. I've defined them as permanent lease in DHCP, but it didn't work. I'll keep an eye on the ip addresses, once similar issues arrise. So I'd propose to close this one and I'll ask to re-open, if the issue occurs again. Thanks,Tom