https://bugs.winehq.org/show_bug.cgi?id=57526
Bug ID: 57526 Summary: Bluetooth driver cannot be disabled. Product: Wine Version: 10.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: hibbsncc1701@gmail.com Distribution: ---
Sidenote: Neither bluetoothapis, bthprops.cpl, or winebth.sys are listed in the bugzilla component list.
When the host system does not have bluez installed (as it lacks a bluetooth controller), wine will spam dbus errors for a non-existent bluez service to the console during start up.
Attempting to disable the message by setting bluetoothapis to disabled in the libraries tab of winecfg does nothing. Disabling the driver causes wine to complain that it cannot load the driver on each startup.
Even for a system with bluez installed, it would be nice to have some option that could disable this support when it's not needed. As bluetooth snooping can be a method of privacy invasion, and a misbehaving app could cause issues with the native apps running on the host.
UsefulRegistryKey maybe? A more proper option would be a checkbox in winecfg, or the stubbed cpl.
https://bugs.winehq.org/show_bug.cgi?id=57526
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- (In reply to Patrick Hibbs from comment #0)
Sidenote: Neither bluetoothapis, bthprops.cpl, or winebth.sys are listed in the bugzilla component list.
When the host system does not have bluez installed (as it lacks a bluetooth controller), wine will spam dbus errors for a non-existent bluez service to the console during start up.
This can and should be fixed.
Even for a system with bluez installed, it would be nice to have some option that could disable this support when it's not needed. As bluetooth snooping can be a method of privacy invasion, and a misbehaving app could cause issues with the native apps running on the host.
If you're concerned about that, a setting in Wine won't save you. We don't do anything that requires special privileges.
https://bugs.winehq.org/show_bug.cgi?id=57526
--- Comment #2 from Patrick Hibbs hibbsncc1701@gmail.com --- (In reply to Zeb Figura from comment #1)
(In reply to Patrick Hibbs from comment #0)
Even for a system with bluez installed, it would be nice to have some option that could disable this support when it's not needed. As bluetooth snooping can be a method of privacy invasion, and a misbehaving app could cause issues with the native apps running on the host.
If you're concerned about that, a setting in Wine won't save you. We don't do anything that requires special privileges.
The main thing I'm more worried about is something similar to the following:
End user is talking with their boss via bluetooth. User runs some Windows app under wine. The Windows app hits a wine bug and tries to reset the bluetooth controller as a result. End user is accused of "hanging up" on their boss.
Keep in mind, the same thing could happen with a potential wifi driver. (And in fact is far more likely to occur.)
Having a means to turn that support off would at least mitigate the risk of such occurrences.
https://bugs.winehq.org/show_bug.cgi?id=57526
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de