Snapcraft should print the path of the stack trace file even when the error report is sent automatically
Metadata
Current evaluation
Issue closed as stale because Sentry integration was removed entirely in snapcraft#5592 (commit 0a120c694).
Resolution: closed stale
Reason: The issue requested printing the stack trace path when Sentry's always_send is enabled. A maintainer closed it as stale, noting that Snapcraft has removed Sentry integration entirely (PR #5592, commit 0a120c694), making the feature obsolete.
Evaluated by: mr-cal-bot
No scores available.
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.6-35b-a3b | — | closed stale | Issue closed as stale because Sentry integration was removed entirely in snapcraft#5592 (commit 0a120c694). | |
| stealth/space-bunny-alpha |
Impact:
0
Quick Win:
0
Complexity:
0
Confidence:
97
Actionability:
98
|
close stale | Legacy Sentry reporting no longer affects trace paths because the core20 reporting subsystem and its always_send behavior were removed from Snapcraft. | |
| stealth/space-bunny-alpha |
Impact:
15
Quick Win:
3
Complexity:
10
Confidence:
98
Actionability:
20
|
close stale | Automatic Sentry reports omit the local stack-trace path; the legacy/core20 error-reporting path that produced it has since been removed from Snapcraft. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
14
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. |
Update history
| Date | Change |
|---|---|
| closed | |
| created |
Related work
-
Superseded By:
snapcraft#5592
(confidence 95%)
PR #5592 removed the Sentry error reporting feature entirely, making the request to print stack trace paths on always_send obsolete.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1767151 Setting SNAPCRAFT_ENABLE_SENTRY= causes stacktrace (empty string value not truthy) | snapcraft (launchpad) | closed | Fixed by removing the legacy Sentry error-reporting stack entirely; SNAPCRAFT_ENABLE_SENTRY is no longer parsed in snapcraft. |