cryptkeeper segfaults at start sometimes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptkeeper (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Vlad Orlov |
Bug Description
[Impact]
An uninitialized variable makes cryptkeeper randomly crash on start
in Trusty.
The fix for it had been applied in newer releases (see bug 1420812),
starting from Vivid. Would be nice to apply it in Trusty as well.
The debdiff which is attached to this report contains the fix.
[Test Case]
Since it's a random crash, it may take several attempts to reproduce
it. So just run cryptkeeper a few times from the terminal. It should
crash right on start if it hits some random value in uninitialized
variable.
[Regression Potential]
None. It had been confirmed that the patched version of cryptkeeper
doesn't crash on start anymore (reported by Xenial users for example).
[Original Description]
I don't understand : Most of the time at launch : segfault but sometimes if you reboot the system it starts without complaining. Sometimes not.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cryptkeeper 0.9.5-5.1ubuntu3
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May 5 02:06:09 2014
SourcePackage: cryptkeeper
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- segfault at opening sometimes reboot = ok + cryptkeeper segfaults at start sometimes |
tags: | added: utopic |
Changed in cryptkeeper (Ubuntu): | |
importance: | Undecided → High |
Changed in cryptkeeper (Debian): | |
status: | Unknown → New |
tags: | added: vivid |
Changed in cryptkeeper (Ubuntu): | |
status: | Confirmed → Triaged |
tags: | added: wily xenial |
Changed in cryptkeeper (Debian): | |
status: | New → Fix Released |
no longer affects: | cryptkeeper (Debian) |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.