Incorrect value of num_burners when hal autodetection fails

Submitted by Lionel Le Folgoc

Assigned to Xfburn Bug Triage

Link to original bug (#7156)

Description

Created attachment 3393 Proposed patch

Hi,

Num_burners is not reset to 0 in the autodetection function that uses libburn. When hal is missing (but support enabled in xfburn), num_burners is set to -1. So, when a burner is found with libburn, num_burners++ gives 0 instead of 1, letting xfburn think no burner is available (see attached patch).

Thanks!

Patch 3393, "Proposed patch":
test.patch

Version: 0.4.3