Icinga / Icinga/icingaweb2-module-pdfexport
Crashdumps fail to be dumped due to permission errors
Open
Nobody has claimed this yet.
bug
- Dominant language
- PHP
- Stars
- 33
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Chrome may try to dump a crashdump:
mkdir /tmp/Crashpad/new: Permission denied (13)
To Reproduce
n/a
Expected behavior
Chrome runs fine anyway. (Depends on the crash of course)
Additional context
There is --crash-dumps-dir which might help if defined.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing PDF export and tracing how Chrome is launched and where its crashdump directory is configured; then determine whether the permission error can be prevented or safely handled, and verify the export still works without the crashdump failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100