You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgraded to Prusaslicer 2.9.0 now via flatpak, used 2.8.x as standalone before.
Printer hostname (octopi.local) is not resolved now. If browsing for it Prusaslicer finds it with the local ip and with the hostname! But when selecting the local IP is used. If manually entering the hostname instead error 6 "cannot resolve hostname pops up".
Seems strange that the hostname can be found by Prusaslicer when browsing but cannot be resolved.
Project file & How to reproduce
GNOME 43.9.
Checklist of files included above
Project file
Screenshot
Version of PrusaSlicer
2.9.0
Operating system
Debian 12 Bookworm,
Printer model
MK3S
The text was updated successfully, but these errors were encountered:
Seems resolved, but think some fixes in prusaslicer could be done.
When manually entering hostname "octopi" instead of octopi.local it works. However the configuration was imported from 2.8.x I had before and there octopi.local did work perfectly.
I think hostname when selecting in Network lookup, should be prioritized over IP address as in this case with DHCP address that will change.
I also wonder what have changed for ".local" to not function anymore.
Description of the bug
Upgraded to Prusaslicer 2.9.0 now via flatpak, used 2.8.x as standalone before.
Printer hostname (octopi.local) is not resolved now. If browsing for it Prusaslicer finds it with the local ip and with the hostname! But when selecting the local IP is used. If manually entering the hostname instead error 6 "cannot resolve hostname pops up".
Seems strange that the hostname can be found by Prusaslicer when browsing but cannot be resolved.
Project file & How to reproduce
GNOME 43.9.
Checklist of files included above
Version of PrusaSlicer
2.9.0
Operating system
Debian 12 Bookworm,
Printer model
MK3S
The text was updated successfully, but these errors were encountered: