Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selected Printer port not kept between session #2740

Closed
gege2b opened this issue Jul 18, 2018 · 1 comment
Closed

Selected Printer port not kept between session #2740

gege2b opened this issue Jul 18, 2018 · 1 comment
Labels
done Done but not yet released improvement Improving functionality, behaviour, UX, ...
Milestone

Comments

@gege2b
Copy link

gege2b commented Jul 18, 2018

Note : this is about this issue

What were you doing?

I was using Virtual printer to test some stuffs

  1. Go to octoprint UI and connect to the virtual printer (of course, virtual printer should be enabled first)
  2. close and repoen the browser tab of octoprint (OR refresh the page)
  3. The selected printer port is not the virtual printer but /dev/whatever (I think it revert to the default printer)

I cannot test with two real printers

What did you expect to happen?

The selected port to be kept

What happened instead?

The selected port switch to, I think, the one of the defaut printer
Manual commands are still sent to the vritual printer

It's not a killer bug, probably a JS thing

Did the same happen when running OctoPrint in safe mode?

Yes

Version of OctoPrint

1.3.9rc3
Same on 1.4-dev
I think it's here since some time, but as I never used virtual printer until now, I didn't notice

Operating System running OctoPrint

raspbian strech 9.3 on rpi3

Printer model & used firmware incl. version

marlin 1.1.8

Browser and version of browser, operating system running browser

Firefox 61 on win10

Link to octoprint.log

octoprint.log

Link to contents of terminal tab or serial.log

n/a

Link to contents of Javascript console in the browser

the copy/paste is a mess but there is neither errors nor warnings, only the usual stuffs

I have read the FAQ.

@GitIssueBot GitIssueBot added the triage This issue needs triage label Jul 18, 2018
@foosel foosel added this to the 1.3.10 milestone Oct 29, 2018
@foosel
Copy link
Member

foosel commented Oct 29, 2018

Should be fixed by the above commit (and was broken at least since 2013). Pushed to maintenance, soon devel, to be released with 1.3.10.

@foosel foosel added done Done but not yet released improvement Improving functionality, behaviour, UX, ... and removed triage This issue needs triage labels Oct 29, 2018
@foosel foosel closed this as completed in 0268caf Dec 10, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
done Done but not yet released improvement Improving functionality, behaviour, UX, ...
Projects
None yet
Development

No branches or pull requests

3 participants