Hardcoded path in recoverable-problem may cause problems in Snappy
Bug #1638716 reported by
Charles Kerr
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| indicator-session (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
As described by mterry in <https:/
> And I left the "/usr/share/
> src/recoverable
> tool anyway. And I wasn't sure there is some plan for snappy to include
> an error reporting tool or what.
I suspect we don't need this recoverable error anymore in indicator-session, so we could remove it. If we do still need it, we need to see if this approach needs any modification in the snappy world
There is also an umbrella ticket for hardcoded paths in the u8 snap: <https:/
Related branches
lp:~charlesk/indicator-session/lp-1638716-recoverable-whoopsie
- Pete Woods (community): Approve
- unity-api-1-bot: Needs Fixing (continuous-integration)
-
Diff: 336 lines (+25/-227)6 files modifiedCMakeLists.txt (+3/-2)
debian/control (+1/-0)
src/CMakeLists.txt (+1/-3)
src/recoverable-problem.c (+0/-167)
src/recoverable-problem.h (+0/-26)
src/service.c (+20/-29)
| description: | updated |
Revision history for this message
| Charles Kerr (charlesk) wrote | #1 |
| Changed in indicator-session (Ubuntu): | |
| status: | Confirmed → Triaged |
| summary: |
- Hardcoded path in recoverable-problem needs evaluation for Snappy + Hardcoded path in recoverable-problem may cause problems in Snappy |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in indicator-session (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Happily recoverable errors are handled in libwhoopsie, so indicator-session can farm out that work.
Similar normalization patch in UAL:
https:/