ERROR: Cannot open file: Permission denied – File Opening Component

When Blender attempts to open a file located in a protected directory, the console emits the message ERROR: Cannot open file: Permission denied and aborts the operation. The current implementation provides no graphical feedback, leaving the user unaware of possible remedies.

Key constraints include the lack of a GUI dialog, absence of automated permission escalation, and the potential for cross‑platform inconsistencies. Users report frustration due to the abrupt halt and lack of guidance on how to resolve the issue.

Unresolved decisions revolve around whether Blender should (1) present a dialog offering to retry or request elevated privileges, (2) suggest alternative file locations, or (3) provide a fallback mechanism for read‑only files. What design pattern should govern the permission‑escalation workflow across Windows, macOS, and Linux?