** Tags added: oem-priority
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected after
connected
Status in Blue
** Changed in: oem-priority
Importance: Critical => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected
I've backported the is_trusted/pair pointer devices changes in a bionic
SRU and used bug #1779289 for the update (the bug here seems like it's
not only about that)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bu
It seems like the bug has been fixed in bluez 5.50-6. My Logitech M336
works now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automa
See bug 1822533 instead.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected after
connected
Status in Bluez U
> This bug is not about suspending and resuming.
The root cause is the same: the key doesn't get stored because it uses
"Connect" instead of "Pair" for SSP devices.
> As mentioned in the bug description, this bug only ever occurred on Intel
> 8265 with the M337 on bionic.
It happens on multiple
As mentioned in the bug description, this bug only ever occurred on
Intel 8265 with the M337 on bionic. All other issues should be discussed
in other bugs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launc
This bug is not about suspending and resuming.
And I can't test resuming because my system becomes too unstable (for
other reasons). As for system reboot, I have always had problems with
some Bluetooth devices reconnecting on reboot. But that problem is not
confined to mice. It happens with audio
No it's not specific to Intel 8265.
Can your M337 reconnect automatically after system suspend or system
reboot?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regressio
I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and
cannot reproduce any bug.
If the problem ever was specific to Intel 8265 then it might have been
fixed in firmware updates already here:
https://launchpad.net/ubuntu/+source/linux-firmware
While comment #50 is interesting,
Added to Trello: https://trello.com/c/4fDA1uYR/291-bug1773897
-regression-logitech-m337-mice-are-automatically-disconnected-after-
connected
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1
Please backport this two MR:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kerne
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Confirmed
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Pack
(In reply to Kai-Heng Feng from comment #9)
> My intention is to ask you to try adding this entry to pin-code-database.xml:
>
See https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Do you folks use gnome-control-center to pair?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected after
connec
My intention is to ask you to try adding this entry to pin-code-database.xml:
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatic
I tried the pairing via the gnome control center, command line (
bluetoothctl ) and via blueman. These were done while in a gnome session
however
All three attempts failed as above.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
Take a look at [1] if gnome-control-center is used:
[1]
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/43
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Tit
(In reply to Kai-Heng Feng from comment #5)
> Do you folks use gnome-control-center to pair?
I certainly did use gnome-control-center.
I've just tried again with Fedora 29 (gnome-control-center-3.30.3-1.fc29.x86_64
+ bluez-5.50-3.fc29.x86_64) and out of five remove, add, force reconnect) I
only
Seems like it's because Logitech Far East mice need to be paired.
Please add this to /usr/share/gnome-bluetooth/pin-code-database.xml:
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773
Please see if this kernel helps:
https://people.canonical.com/~khfeng/lp1773897/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automa
I too have had the same issue...
Notebook: Dell XPS 13 9360
bios: tested with 2.9.1 and 2.10.0
OS: Debian stretch 9.8
Kernel: 4.9.0-8 debian 4.9.144-3
Wi-Fi/BT module: Intel Dual Band wirelss AC 8265, rev=0x230
Firmware: iwlwifi-8265-22.ucode
BlueZ: 5.43-2+deb9u1
BT Mouse: Logitech MX anywhere 2
Same issue with a fresh new install of Mint 19.1 (booted from USB) on a
Dell Inspiron 7778 and bluetooth mouse HP Z5000. No problems with Mint
18.3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
Mime is M585 and seems like it works with Bluez 5.50.
There are lots of fixes in Bluez master, maybe some commits fix the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Titl
Ah indeed...
$ LANG=C apt policy bluez
bluez:
Installed: 5.50-0ubuntu1
Candidate: 5.50-0ubuntu1
Version table:
*** 5.50-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
In that case I don't think I can confirm this fixes
Cosmic already has BlueZ 5.50
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected after
connected
Status in Bl
@Feng could you please rebuild for cosmic, too? I'll try it out then.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disc
Seems like Bluez 5.50 fixes the issue, tried re-repairing BT mouse 5
times and it seems to work so far.
I guess this commit fixes the issue:
commit a07eb3a5e96d7f23a2aa554088d3cc3a9e57744f
Author: Andrzej Kaczmarek
Date: Thu Mar 22 16:21:00 2018 +0100
shared/gatt-client: Fix discovery of d
I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
It takes me disabling bluetooth, deleting the profile, re-enabling
bluetooth, and putting the mouse back in pairing mode
lsusb says "Bus 002 Device 003: ID 8087:07dc Intel Corp." here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnect
Michał, does this happen to intel Bluetooth USB controller?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected a
I'm back to having to re-pair a handful of times each boot. It seems
every once in a while the pairing "sticks" and works until I have to
reconnect it again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.lau
I can also reproduce this bug.
Notebook: Dell XPS 13 (9370)
Wi-Fi/BT module: not sure...
bluez: 5.50
BT mouse: logitech M336 (M337)
Log:
[bluetooth]# paired-devices
Device 34:88:5D:92:FC:0C Bluetooth Mouse M336/M337/M535
// try to connect the mouse
[bluetooth]# connect 34:88:5D:92:FC:0C
Attempti
Not sure what's changed, but I've recently had much better luck with the
mouse connecting properly by itself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] L
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199873.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
** Summary changed:
- [regression] Bluetooth 3.0 mouses are automatically disconnected after
connected
+ [regression] Logitech M337 mice are automatically disconnected after connected
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
The attached file is the output of "journalctl -b".
** Attachment added: "journalctl-b.log"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/+attachment/5145906/+files/journalctl-b.log
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145898/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145900/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145903/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145902/+files/rfkill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145901/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145899/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
** Also affects: bluez via
https://bugzilla.kernel.org/show_bug.cgi?id=199873
Importance: Unknown
Status: Unknown
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Bluetooth 3.0 mouses are automatically disconnected after connected
+ [regression] B
Filed a upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=199873
** Bug watch added: Linux Kernel Bug Tracker #199873
https://bugzilla.kernel.org/show_bug.cgi?id=199873
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in U
This bug still can be reproduced in BlueZ 5.49.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
Bluetooth 3.0 mouses are automatically disconnected after connected
Status
Thanks. Please try 5.49
(https://launchpad.net/~bluetooth/+archive/ubuntu/bluez). If the problem
continues in 5.49 then please report the bug upstream here:
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth
mentioning that it seems to be a regression starting at 6b34bd
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145893/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145897/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145896/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145894/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1773897/+attachment/5145895/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
The BT 3.0 mouse is disconnected automatically after connected with the
notebook.
The fail rate is around 9/10.
1. The bug only occurs on the machine with intel 8265 module.
I got three D
Please answer all the above questions, and if you find it's still a
problem in 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez)
then please report the bug upstream here:
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth
--
You received this bug notificati
More information:
This issue does not cause by single commit.
since "6b34bdd96 ("shared/gatt-client: Fix not removing services that had
disappeared", 2017-05-24)", this bug can be reproduced with low fail rate
(around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I do
Another idea is to try installing 'linux-firmware', if not already, to
ensure the wifi chip's firmware is up to date.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
Blueto
In the meantime, please run 'apport-collect 1773897' on the problematic
machine to send us more information about it.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: oem-priority
Status: New => Incomplete
** Changed in: bluez (Ubuntu)
Importance: Undecided
You may also wish to try a preview of BlueZ 5.49 from here:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
Bluetooth
Please also attach the kernel log (dmesg) and the system log (journalctl
-b) from the affected machine, capturing a period of time when the
problem happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.laun
Sounds similar to bug 1771733 (which will hopefully expire) or bug
1651433 (which is also XPS 13).
Fortunately I have multiple Logitech M337's here, so I will test them
with various laptops over the coming days.
--
You received this bug notification because you are a member of Kernel
Packages, w
The attached file is the .snoop when I reproduced this bug.
** Attachment added: "hcitrace.snoop"
https://bugs.launchpad.net/oem-priority/+bug/1773897/+attachment/5145809/+files/hcitrace.snoop
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notifica
Public bug reported:
The BT 3.0 mouse is disconnected automatically after connected with the
notebook.
The fail rate is around 9/10.
1. The bug only occurs on the machine with intel 8265 module.
I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
This bug can not be rep
63 matches
Mail list logo
