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

Cannot open files using Cura on linux Chromebook #12268

Closed
2 tasks
jasondilts opened this issue May 20, 2022 · 3 comments
Closed
2 tasks

Cannot open files using Cura on linux Chromebook #12268

jasondilts opened this issue May 20, 2022 · 3 comments
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.

Comments

@jasondilts
Copy link

Application Version

5.0.0

Platform

Linux

Printer

Ender 3 Pro

Reproduction steps

  1. Downloaded Cura 5.0.0
  2. Attempted to open a file to slice
  3. Would not open when clicking on the folder icon
  4. Would not open when clicking File, open File

Actual results

Nothing happens, can't open a file to slice. Everything worked fine in the previous version of Cura

Expected results

Expected to be able to open a file and slice it.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

none

@jasondilts jasondilts added the Type: Bug The code does not produce the intended behavior. label May 20, 2022
@gleonard3
Copy link

This was also reported in Beta 5, Issue #11874

@Vandresc
Copy link
Contributor

Duplicate of #12266.

Thank you for your feedback, we will bring this up with the rest of the team.

@Vandresc Vandresc added the Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. label May 30, 2022
@MariMakes
Copy link
Contributor

Hey @jasondilts

We don't support Chrome OS and unfortunately we are not planning developing Cura for Chromebooks any time soon.
But if your issue is indeed a duplicate of #12266, than you can follow the progress there.

I will close this issue since it's a duplicate, I hope you understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

4 participants