fails to start in trusty - missing package dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
smc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
The smc package in trusty is faulty. It needs to declare a dependency on the ttf-dejavu-core package. If the package is not installed, the program fails to start.
Vivid is not affected since this problem was fixed in Debian in
smc (1.9+git2012112
* Non-maintainer upload.
* Fix "/usr/share/
(Closes: #758427):
- smc-data needs to depend on fonts-dejavu-core
- update smc-data.links to the fonts in this package and not in the
transitional package ttf-dejavu-core
* Fix "desktop file category key is incomplete". Applying patch from Markus
Koschany, but omitting the character name as it could be a trademark.
(Closes: #738030)
-- Tobias Frost <email address hidden> Tue, 19 Aug 2014 10:08:44 +0000
SRU TEST CASE
Install smc in a trusty environment that does NOT have the ttf-dejavu-core package installed. Run smc from the command line. The program aborts with an error about missing fonts. Now install said package and things will go fine.
Regression potential
None. The program currently fails to start if the fonts are missing. This is fixed by adding the package to the depends for smc-data.
Changed in smc (Ubuntu Trusty): | |
milestone: | none → ubuntu-14.04.2 |
Changed in smc (Ubuntu): | |
importance: | Undecided → High |
Changed in smc (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in smc (Ubuntu): | |
milestone: | ubuntu-14.04.2 → none |
Thank you for taking the time to work on this bug and helping to make Ubuntu better.
I couldn't actually reproduce this as my test environment is a server system, but the bug and the fix both seem trivial enough that I won't worry about it; particularly because Debian have already done the same.
Uploaded with a couple of minor tweaks. It didn't seem worth delaying while you got back to me on these:
1) The version number for a Trusty SRU is best being 1.9+git20121121 -1ubuntu1. 1 here, not ubuntu2, just to make it clear that this is an SRU and to follow the usual pattern. ubuntu2 would probably have been fine in this case though since future releases have superceded the ubuntu1 version.
2) I've added to your changelog entry " to fix failure on startup": it's useful to say _why_ in a changelog entry, as well as _what_, to make it easier for future readers of the changelog.
Accepting the Trusty nomination and marking Fix Released in the development release based on the Debian changelog you posted (I can see that version is synced).