fails to start in trusty - missing package dependency

Bug #1403472 reported by Rolf Leggewie
12
This bug affects 1 person
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+git20121121-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Fix "/usr/share/games/smc/gui/font/default_bold.ttf does not exist"
    (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.

Revision history for this message
Rolf Leggewie (r0lf) wrote :
Revision history for this message
Robie Basak (racb) wrote :

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).

Changed in smc (Ubuntu):
status: New → Fix Released
Changed in smc (Ubuntu Trusty):
status: New → In Progress
Rolf Leggewie (r0lf)
Changed in smc (Ubuntu Trusty):
milestone: none → ubuntu-14.04.2
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thanks, Robie. Will these require a verification-done tag?

Revision history for this message
Robie Basak (racb) wrote : Re: [Bug 1403472] Re: fails to start in trusty - missing package dependency

Yes, but only after the SRU team accept the package into trusty-proposed and you have verified this build fixes the problem please. Right now it's still in the SRU queue awaiting review I think?

Revision history for this message
Brian Murray (brian-murray) wrote :

Shouldn't this also be fixed in Utopic?

Changed in smc (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Rolf, or anyone else affected,

Accepted smc into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/smc/1.9+git20121121-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I can verify the fix for trusty. Thank you.

Technically, yes, this should be fixed in Utopic as well. But is it really worth the trouble with the shortened life cycle of dev versions these days?

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package smc - 1.9+git20121121-1ubuntu1.1

---------------
smc (1.9+git20121121-1ubuntu1.1) trusty-proposed; urgency=medium

  * add ttf-dejavu-core to run-time dependencies to fix failure on
    startup. LP: #1403472
 -- Rolf Leggewie <email address hidden> Wed, 17 Dec 2014 20:18:44 +0800

Changed in smc (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for smc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mathew Hodson (mhodson)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.