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

PermissionError with faulthandler on QGIS 3.40.0 (MacBook Air M1, macOS Sequoia 15.1, MacPorts) #59439

Closed
2 tasks done
K-Dai48 opened this issue Nov 13, 2024 · 1 comment
Closed
2 tasks done
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@K-Dai48
Copy link

K-Dai48 commented Nov 13, 2024

What is the bug or the crash?

An error occurred while executing the following code:
faulthandler.enable(file=qgis.utils.__qgis_fault_handler_file)

Traceback (most recent call last):
File "", line 1, in
PermissionError: [Errno 1] Operation not permitted

Steps to reproduce the issue

  1. Open QGIS3 Desktop.
  2. Observe that a Python error window appears immediately upon startup.

Versions

QGIS version: 3.40.0-Bratislava
OS: macOS Sequoia 15.1
Device: MacBook Air (M1)
Installation method: MacPorts

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

I’m using a MacBook Air (M1) with macOS Sequoia 15.1 and installed QGIS 3.40.0-Bratislava via MacPorts. To troubleshoot this issue, I’ve tried the following steps:
• Checked directory permissions to ensure that QGIS has write access.
• Attempted to set up faulthandler to capture error logs in an external file.
• Created and tested with a new QGIS profile to rule out profile-related issues.
• Granted QGIS “Full Disk Access” in macOS security settings.
• Reinstalled QGIS to ensure a clean installation.

Despite these efforts, the error persists on every startup. Any guidance on resolving this issue would be greatly appreciated. Thank you.

@K-Dai48 K-Dai48 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Nov 13, 2024
@agiudiceandrea
Copy link
Contributor

The issue has been already previously reported at #52987.

@agiudiceandrea agiudiceandrea closed this as not planned Won't fix, can't repro, duplicate, stale Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

2 participants