Snapcraft should print the path of the stack trace file even when the error report is sent automatically
Metadata
Current evaluation
Feature request to always print the local stack trace file path when Snapcraft auto-sends error reports. Open since 2018 with zero comments, no labels, and no maintainer interaction.
Suggested action: close stale
Reason: The issue is 2823 days old (~7.7 years) with zero comments, no labels, and no maintainer interaction. It is a minor UX improvement (printing a file path) for a debugging workflow that has likely been superseded by the current error-reporting architecture in snapcraft. The original code paths referenced (Sentry.always_send, /tmp/tmpXXXXXXXX/trace.txt) are from a much older version and the behavior may have already changed.
Impact:
15
Quick Win:
13.5
Staleness:
95
Complexity:
10
Confidence:
70
Support Request:
10
Issue body
Refer the following output:
```
Sorry, an error occurred in Snapcraft.
Sending an error report because ALWAYS was selected in a past prompt.
This behavior can be changed by changing the always_send entry in /home/ubuntu/.config/snapcraft/cli.cfg.
Thank you, sent.
```
Currently, if `Sentry.always_send` is set to `true` Snapcraft will not print the path of the stored stack trace file(/tmp/tmpXXXXXXXX/trace.txt). Snapcraft should always print it for debugging purposes.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
13.5
Staleness:
95
Complexity:
10
Confidence:
70
Support Request:
10
|
close stale | Feature request to always print the local stack trace file path when Snapcraft auto-sends error reports. Open since 2018 with zero comments, no labels, and no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
90
Support Request:
10
|
close stale | Feature request to always print the local stack trace file path when Snapcraft automatically sends error reports. Issue has been inactive for over 7 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Request to always print the stack trace file path in Snapcraft's error output, even when automatic error reporting is enabled. Unaddressed for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
99
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Feature request to always print the stack trace file path during automatic error reporting. The issue is extremely stale, has no maintainer engagement, and likely applies to an outdated version of the error handling system. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
15
|
close stale | Feature request to always print stack trace file paths during automatic error reporting. Unattended for over 7 years with no maintainer response or labels. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1815171 Snapcraft could show the traceback rather than just offer to send it to LP | snapcraft (launchpad) | open | Feature request to display the full Python traceback in the terminal when snapcraft crashes, rather than only offering to anonymously send it to Launchpad. Open since 2018, no maintainer activity, and the referenced snapcraft 3.1 error flow no longer exists in the current codebase. |