Your message dated Tue, 4 Nov 2025 17:24:49 +0100
with message-id <[email protected]>
and subject line Duplicate
has caused the Debian Bug report #1115161,
regarding bluez: Bluetooth stops working when coming from sleep
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1115161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115161
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bluez
Version: 5.82-1.1
Severity: important
Tags: a11y
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Bluetooth is not able to start when coming from sleep. Bluetooth works when
starting the system. As per the logs, the issue is with the configuration
directory of bluetooth having different file ownership. Its something to do
with bluez creating the directory but bluetooth service still has no rights for
it.
Sep 01 17:51:00 user systemd[1]: Starting bluetooth.service - Bluetooth
service...
Sep 01 17:51:00 user (uetoothd)[999]: bluetooth.service: ConfigurationDirectory
'bluetooth' ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Sep 01 17:51:00 user bluetoothd[999]: Bluetooth daemon 5.82
Sep 01 17:51:00 user bluetoothd[999]: Starting SDP server
Sep 01 17:51:00 user systemd[1]: Started bluetooth.service - Bluetooth service.
Sep 01 17:51:00 user bluetoothd[999]: Bluetooth management interface 1.23
initialized
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo sed -i
's/ConfigurationDirectoryMode=0555/ConfigurationDirectoryMode=0755/g'
/lib/systemd/system/bluetooth.service
sudo systemctl daemon-reload
sudo modprobe -r btusb
sudo modprobe btusb
* What was the outcome of this action?
This will atleast get bluetooth working normally again without restarting the
system.
* What outcome did you expect instead?
The bluetooth.service should have that ownership already to the configuration
directory.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.43+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bluez depends on:
ii adduser 3.152
ii dbus [default-dbus-system-bus] 1.16.2-2
ii init-system-helpers 1.69~deb13u1
ii kmod 34.2-2
ii libasound2t64 1.2.14-1
ii libc6 2.41-12
ii libdbus-1-3 1.16.2-2
ii libdw1t64 0.192-4
ii libglib2.0-0t64 2.84.4-3~deb13u1
ii libreadline8t64 8.2-6
ii libudev1 257.8-1~deb13u2
ii udev 257.8-1~deb13u2
bluez recommends no packages.
Versions of packages bluez suggests:
pn pulseaudio-module-bluetooth <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
This bug presents two issues, both duplicates:
- bad file ownership: duplicate of bug 1017988
- needs to reload btusb to make it work (again): duplicate of bug 1117497
Thus, closing.
--- End Message ---
