Opened 3 years ago

Closed 3 years ago

#11650 closed defect (fixed)

Automatic diagnostic sequence suggests users can return to menu when XO shuts off instead

Reported by: greenfeld Owned by: Quozl
Priority: low Milestone: 1.75-firmware
Component: ofw - open firmware Version: Development build as of this date
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: no action
Verified: no

Description

Q4D04 includes the fix for #11612 which allows the left-rocker initiated automatic test sequence to fully complete without requiring the user to use the arrow keys to manually select tests.

However when the end of the automatic sequence is reached, a message appears that says to "Press any key to return to the menu."

But if a user just let the automatic countdown start the test sequence, one cannot return to the menu; instead the XO powers off.

If possible we should clarify this message.

Change History (6)

comment:1 Changed 3 years ago by Quozl

  • Action Needed changed from diagnose to code
  • Owner changed from wmb@… to Quozl
  • Status changed from new to assigned
  • Type changed from enhancement to defect

comment:2 Changed 3 years ago by Quozl

  • Action Needed changed from code to add to release
  • Milestone changed from Not Triaged to 1.75-firmware

Fixed in svn 2876.

comment:3 Changed 3 years ago by martin.langhoff

James -- is this in an rpm already that I can add to an OS build? If so, mark it "add to build".

If it's in a commit that needs to go into an OFW release, please use a different action ("package" is probably the most appropriate).

The scope/perspective for the "action" field is is the overall OS release -- that's how we treat it within this project...

thanks!

comment:4 Changed 3 years ago by Quozl

  • Cc wmb@… added

no, for the 1.75-firmware milestone, and other -firmware milestones, i have been using add-to-release and other next action values in their literal sense, relating only to openfirmware. the ticket will close on a release of openfirmware, unless testing of the fix was warranted.

if the bug reporter or triage had placed this ticket in the 11.3.1 milestone, then i would expect to have this ticket in package state.

if you would like the ticket fixed in 11.3.1, then please say so.

comment:5 Changed 3 years ago by Quozl

  • Action Needed changed from add to release to no action
  • Cc wmb@… removed

Is in Q4D05.

comment:6 Changed 3 years ago by Quozl

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.