Hello, Dave Mielke (2011/04/23 10:51 -0400): > >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 ? > > Thanks. It was a bug. Please retest to ensure it's been fixed.
Yes, the fix works, thanks. Please note however that compiling brltty with beeper support disabled now produces the following warning: In file included from ./sys_linux.c:142:0: ./sys_beep_none.h:19:2: warning: #warning console beep support not available on this platform In file included from ./sys_linux.c:142:0: ./sys_beep_none.h:19:2: warning: #warning console beep support not available on this platform This warning should not be displayed when beeper support has been explicitly disabled at configure time. This is the same problem I already reported regarding illegitimate warnings displayed when USB and bluetooth support are disabled. Sébastien. _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
