[BRLTTY] brltty attempts to use beeper even when configured with --disable-beeper-support

[Sébastien Hinderer]

Hello,

In response to Dave's message asking all of us to test the last
development release, I notice the following behaviour:
although brltty is configured with --disable-beeper-support,
getDefaultTuneDevice is called, which calls canBeep which in turn calls
getConsole, the result being permission error messages in the logs since
the user running brltty is not allowed to open the console in write mode.
Is this an intended behaviour or a bug ?

Cheers,
Sébastien.