Open nkuck opened 5 years ago
Please fill in the entire template. This is not nearly enough information for us to know what the actual problem is.
In my experience, Github does abort quite easily. Look, I can demonstrate it here with this issue.
(Please fill in the issue template. It puts a warning there that we close your issue if it's not filled in.)
When you fill in, make sure you remove the <!--
and -->
bits. Don't put your text in between them, because that will make the text invisible.
In the comment markup of the message there was indeed a properly filled out template! I removed the comment markup so that it's actually visible to people who can't edit stuff...
So I'm assuming that this has to do with USB printing. I can't reproduce this though. I don't have your printer, but I tried with an Ultimaker 2+ using these steps:
Thanks for the feedback on my issue presentation. Here is/are the issue(s): With Cura started, and connected via USB to my Prusa i3 clone, it is sometimes recognized, sometimes not (issue #1). My computer is a MacBook Pro running latest iOS OS Mohave V 10.14.4 Beta (18E184e). Issue #2: Normally after I click on Prepare, I just get a Save to File option, and not Print over USB, as I mentioned above, the computer/Cura do not always talk to each other. When/if I get a Print option, it usually follows that I will get an Abort option which, when selected, nothing happens. The print operation will just continue. Running Marlin FW Bugfix 1.1.x
Maybe you could share a log? Maybe that shows something?
Sure. Which log would be useful?
Live simply! On Feb 14, 2019, 4:00 AM -0500, Ghostkeeper notifications@github.com, wrote:
Maybe you could share a log? Maybe that shows something? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Cura's GUI log file. See https://github.com/Ultimaker/Cura#logging-issues
I tried it this morning and all seems fine. Not sure why. Thanks for your assistance and interest.
On Feb 14, 2019, at 6:56 AM, Ghostkeeper notifications@github.com wrote:
Cura's GUI log file. See https://github.com/Ultimaker/Cura#logging-issues https://github.com/Ultimaker/Cura#logging-issues — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Ultimaker/Cura/issues/5299#issuecomment-463600790, or mute the thread https://github.com/notifications/unsubscribe-auth/AJrd8qbhHdFz_kAJr4x0OwCPmVqzNxPKks5vNU7igaJpZM4a33xv.
Tried it again but failed. Files are attached. Thanks for the review.
On Feb 14, 2019, at 6:56 AM, Ghostkeeper notifications@github.com wrote:
Cura's GUI log file. See https://github.com/Ultimaker/Cura#logging-issues https://github.com/Ultimaker/Cura#logging-issues — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Ultimaker/Cura/issues/5299#issuecomment-463600790, or mute the thread https://github.com/notifications/unsubscribe-auth/AJrd8qbhHdFz_kAJr4x0OwCPmVqzNxPKks5vNU7igaJpZM4a33xv.
Attachments to the e-mail are not published via Github. Please go to the Github website and upload it there: https://github.com/Ultimaker/Cura/issues/5299
After a slice operation, I get the choice to save or to print the file. If I select Print, I am presented with an Abort option which, if selected, does not quit.
Application Version 3.6
Platform Macintosh running Marlin and OSX 10.14.4
Printer Zonestar (Prusa i3).
Steps to Reproduce Simply open a file, start slicer, and then print, then hit abort
Actual Results nothing...continues to print
Expected results printing ceases
Additional Information none