1573160 : PyCharm kann Datei nicht schreiben obwohl ich genung Platz in HomeDir habe und nichts mit Berechtigungen gemacht

Created: 2026-02-03T07:41:42Z - current status: new

Here is the anonymized and summarized report:

Summary of the Issue

A user reports that PyCharm (a JetBrains IDE) suddenly fails to save files, including: - Configuration files (e.g., actionSummary.xml in ~/.config/JetBrains/PyCharmCE2024.3/options/). - Project files (e.g., Python scripts in ~/PycharmProjects/).

The error persists even after: - Verifying sufficient disk space in the home directory. - Testing manual file creation in the same directories (which works). - Trying a new PyCharm installation.

The issue appeared unexpectedly after the last use in December 2025, with no prior problems.

Possible Causes & Solutions

  1. File Permissions or Ownership Issues
  2. PyCharm may lack write permissions for its own configuration directory or project files.

  3. Solution:

    • Check permissions: bash ls -ld ~/.config/JetBrains/PyCharmCE2024.3/options/ ls -l ~/.config/JetBrains/PyCharmCE2024.3/options/actionSummary.xml
    • Reset ownership/permissions if needed: bash chown -R [USERNAME]:[USERGROUP] ~/.config/JetBrains/ chmod -R u+rw ~/.config/JetBrains/

  4. Filesystem Quota or Inode Limits

  5. While disk space is available, the user might have hit an inode limit (common on shared filesystems like /home).

  6. Solution:

    • Check inode usage: bash df -i ~
    • If inodes are exhausted, clean up small/unnecessary files (e.g., cache, temporary files).

  7. Corrupted PyCharm Configuration

  8. The actionSummary.xml file or its backup (~) might be corrupted.

  9. Solution:

    • Rename the problematic file to force PyCharm to recreate it: bash mv ~/.config/JetBrains/PyCharmCE2024.3/options/actionSummary.xml{,.bak}
    • Restart PyCharm.

  10. Filesystem-Level Issues

  11. The underlying filesystem (e.g., NFS) might have temporary issues.

  12. Solution:

    • Contact system administrators to verify filesystem health.

  13. SELinux/AppArmor Restrictions (Unlikely on Maxwell)

  14. Security modules might block PyCharm’s file operations.
  15. Solution:
    • Check for denials in system logs (e.g., /var/log/audit/audit.log).
  1. Test with a minimal PyCharm project in a new directory (e.g., ~/test_pycharm/) to isolate the issue.
  2. Run PyCharm from the command line to capture verbose error logs: bash /path/to/pycharm/bin/pycharm.sh
  3. Check for system-wide updates that might have affected PyCharm’s dependencies (e.g., Java, libraries).

Sources

  • No direct context from the provided Maxwell documentation was applicable to this issue. The solutions are based on general troubleshooting practices for JetBrains IDEs and shared filesystems.