Ubuntu
a7xpg package

push button to start message in a7xpg is ambiguous

Bug #591847 reported by xteejx
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
a7xpg (Debian)
Fix Released
Unknown
a7xpg (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: a7xpg

When starting to run the game a message appears saying "PUSH BUTTON TO START" but doesn't help because it doesn't tell you _which_ button to push!

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: a7xpg 0.11.dfsg1-5
ProcVersionSignature: Ubuntu 2.6.35-1.1-generic 2.6.35-rc1
Uname: Linux 2.6.35-1-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: c4ec36026e45b9e7d8a473844878a77c
CheckboxSystem: 2e4ab5fb96eeb897d439b8ef1239668e
Date: Wed Jun 9 18:17:24 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: a7xpg

Related branches

lp:ubuntu/natty/a7xpg
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :
Changed in a7xpg (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package a7xpg - 0.11.dfsg1-5ubuntu1

---------------
a7xpg (0.11.dfsg1-5ubuntu1) natty; urgency=low

  * debian/patches/start_game_string.patch: Changes ambiguous "push button
    to start" to "push left CTRL to start" (LP: #591847)
 -- Roy Jamison <email address hidden> Wed, 09 Jun 2010 18:12:42 +0100

Changed in a7xpg (Ubuntu):
status: New → Fix Released
Revision history for this message
Evan Broder (broder) wrote :

Thanks for your contribution! I've just sponsored it into Natty. I edited the changelog to re-target the upload to natty instead of maverick, and I added the fields from the Debian Patch Tagging Guidelines (http://dep.debian.net/deps/dep3/) so we can more easily keep track of the patch. Other than that the patch looked good.

I've also submitted the patch to Debian using the submittodebian tool in ubuntu-dev-tools. This is something that you can do yourself in the future. Especially for packages where the Debian maintainers are responsive (which is especially common for packages maintained by a team) and where there aren't already Ubuntu-specific changes, submitting patches to Debian can be the fastest way to get changes in.

Also, when you have a debdiff that's ready to be uploaded, you should subscribe ubuntu-sponsors (as per https://wiki.ubuntu.com/SponsorshipProcess). That will make sure that the patch gets in front of Ubuntu sponsors so it can be handled more quickly on our side.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you Evan for sponsoring this patch. It was created before I fully understood the MOTU process and I had forgotten about it! Once again thank you for pushing this through. Much appreciated :)

Bug Watch Updater (bug-watch-updater)
Changed in a7xpg (Debian):
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in a7xpg (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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