I mailed the developer of "brltty" about this bug and he has proposed the next solution:
Dave Mielke <email address hidden> wrote:
>Strictly speaking, yes, brltty is causing the problem. An easy solution,
>though, would be for Ubuntu to give brltty's udev file an earlier position in
>the udev rules file processing order so that the generic rule will take
>precedence. Then there'd only be a conflict if a brltty user also has one of
>those other devices. That could happen, of course, but it'd be far less common
>than all users being impacted by the current problem.
Anyway thank you all for fixing this bug. Love this community.
I mailed the developer of "brltty" about this bug and he has proposed the next solution:
Dave Mielke <email address hidden> wrote:
>Strictly speaking, yes, brltty is causing the problem. An easy solution,
>though, would be for Ubuntu to give brltty's udev file an earlier position in
>the udev rules file processing order so that the generic rule will take
>precedence. Then there'd only be a conflict if a brltty user also has one of
>those other devices. That could happen, of course, but it'd be far less common
>than all users being impacted by the current problem.
Anyway thank you all for fixing this bug. Love this community.