[Bug 57526] New: Bluetooth driver cannot be disabled.
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(a)winehq.org Reporter: hibbsncc1701(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57526 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zeb Figura <z.figura12(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57526 --- Comment #2 from Patrick Hibbs <hibbsncc1701(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57526 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57526 --- Comment #3 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- The error message has changed slightly, but is still present in Wine-10.0-rc5. It prints: err:winebth:bluez_dbus_loop Error getting object list from BlueZ: 'org.freedesktop.DBus.Error.TimedOut': 'Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)' -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57526 Vibhav Pant <vibhavp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vibhavp(a)gmail.com --- Comment #4 from Vibhav Pant <vibhavp(a)gmail.com> --- (In reply to Patrick Hibbs from comment #3)
The error message has changed slightly, but is still present in Wine-10.0-rc5.
It prints: err:winebth:bluez_dbus_loop Error getting object list from BlueZ: 'org.freedesktop.DBus.Error.TimedOut': 'Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)'
This was fixed in 49a0e297fffe0d7a1f125cfc31f4875a71a918d4. (In reply to Patrick Hibbs from comment #2)
(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.
Neither the current Bluetooth stack driver nor user-mode Bluetooth APIs provide a way to reset the underlying controller, AFAIK. There is IOCTL_BTH_HCI_VENDOR_COMMAND, which allows sending vendor-specific HCI commands to the controller, but since sending raw HCI data on Linux requires elevated privileges, it's unlikely to be implemented on Wine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla