Your message dated Fri, 09 Sep 2016 17:06:43 +0200 with message-id <[email protected]> and subject line Re: gnome-bluetooth: bluetooth softblocked even after toggling switch to on has caused the Debian Bug report #805345, regarding gnome-bluetooth: bluetooth softblocked even after toggling switch to on 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.) -- 805345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805345 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-bluetooth Version: 3.18.1-1 Severity: important Dear Maintainer, * What led up to the situation? I upgraded to gnome-bluetooth 3.18.X and it has persisted ever since. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? Every time I toggle bluetooth off through the GUI (or applet), it soft-blocks my sony-bluetooth switch (as it should) and removes the hci0 switch. But, when I turn it on, it un-soft-blocks sony-bluetooth and creates the hci0 switch properly, but that switch is soft-blocked still. This switch should be un-soft-blocked when I toggle the bluetooth to the "on" position as well. Since it stays soft-blocked, It then shows remembered bluetooth devices (and the toggle appears in the "on" position), but attempting to connect to a remembered device fails immediately (clicking the toggle does nothing). Therefore, I have to manually issue a "sudo rfkill unblock bluetooth" from the terminal. Once I have done that, bluetooth works as desired... until I toggle off and on again, in which case, rinse and repeat! I can issue a "sudo rfkill unblock bluetooth" every time I toggle my bluetooth on through the GUI menu to effectively fix the problem. But, this is not how the package should work. -- System Information: Debian Release: stretch/sid APT prefers testing-proposed-updates APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (600, 'unstable'), (500, 'experimental'), (450, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3-0.dmz.2-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-bluetooth depends on: ii bluez 5.36-1 ii bluez-obexd 5.36-1 ii libatk1.0-0 2.18.0-1 ii libc6 2.19-22 ii libcairo-gobject2 1.14.4-1 ii libcairo2 1.14.4-1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.32.2-1 ii libglib2.0-0 2.46.2-1 ii libgnome-bluetooth13 3.18.1-1 ii libgtk-3-0 3.18.2-1 ii libnotify4 0.7.6-2 ii libpam-systemd 227-2 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libudev1 227-2 ii libx11-6 2:1.6.3-1 ii udev 227-2 Versions of packages gnome-bluetooth recommends: ii gnome-control-center 1:3.18.2-1 ii gvfs-backends 1.26.2-1 Versions of packages gnome-bluetooth suggests: ii gnome-user-share 3.18.0-1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.21.90-2 Hi! With the current gnome-settings-daemon available in testing (version 3.21.90-2), turning the bluetooth device on/off via the Bluetooth panel of GNOME's control center works flawlessly for me, but only if I stop systemd-rfkill like this: systemctl stop systemd-rfkill.socket systemctl stop systemd-rfkill The systemd bug will be tracked in [0]. Since there doesn't seem to be a bug in gnome-bluetooth/gnome-settings-daemon anymore, I'm closing this bug now. However, please feel free to reopen if necessary! Best regards Alexander Kurtz [0] https://github.com/systemd/systemd/issues/4117
signature.asc
Description: This is a digitally signed message part
--- End Message ---
