repowerd crashes on xenial/arm64
Bug #1613602 reported by
Jean-Baptiste Lallement
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Unassigned | ||
repowerd |
Invalid
|
Undecided
|
Unassigned |
Bug Description
xenial/arm64/frieza channel ubuntu-
repowerd crashes on boot with the crash file attached
According to vicamo it crashes in glibc timezone functions. It could be the same root cause than bug 1613605.
description: | updated |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in repowerd: | |
status: | New → Invalid |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
From the attached backtrace (and also the backtrace of the related bug 1613605), this doesn't seem to be a problem caused by repowerd (or USC/Mir). It's just exhibited in these two programs because they try to log with timestamps, which indirectly involve timezone calculations (inside libc, TZ calculations are not performed explicitly by either repowerd or USC).
repowerd in particular doesn't even handle timestamps itself, it just calls the vsyslog() function, which adds timestamps internally.