All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 209745] Bluetooth connection to Logitech MX Master 2S lost after each reboot
Date: Tue, 21 Jun 2022 09:05:57 +0000	[thread overview]
Message-ID: <bug-209745-62941-NS7fxrZ9v5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209745-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209745

--- Comment #27 from Krzysztof.Krason@gmail.com ---
Just adding one another note.
I didn't have the issue for few months (I'm not sure what I did back then) and
now when I upgraded to kernel 5.18.5 the issue is back :(

I need to manually connect to my mouse (MX Master 3) and also keyboard (MX Keys
Mini) and also my bluetooth set (Jabra Elite Active 65t). So it looks like a
general issue with bluetooth.

I'm on old Ubuntu 20.04.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-06-21  9:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 12:00 [Bug 209745] New: Bluetooth connection to Logitech MX Master 2S lost after each reboot bugzilla-daemon
2020-10-19 13:44 ` [Bug 209745] " bugzilla-daemon
2020-10-19 15:18 ` bugzilla-daemon
2020-10-19 22:39 ` bugzilla-daemon
2020-10-27  8:38 ` bugzilla-daemon
2020-10-27 15:34 ` bugzilla-daemon
2020-10-27 15:38 ` bugzilla-daemon
2020-10-28  8:59 ` bugzilla-daemon
2020-10-28 12:55 ` bugzilla-daemon
2020-11-13 16:21 ` bugzilla-daemon
2020-11-15  2:55 ` bugzilla-daemon
2020-11-15  8:01 ` bugzilla-daemon
2020-11-19 20:08 ` bugzilla-daemon
2020-12-15  5:38 ` bugzilla-daemon
2020-12-16  3:09 ` bugzilla-daemon
2020-12-16 13:33 ` bugzilla-daemon
2020-12-16 14:42 ` bugzilla-daemon
2020-12-28 16:36 ` bugzilla-daemon
2020-12-30 13:21 ` bugzilla-daemon
2022-02-09  6:30 ` bugzilla-daemon
2022-06-07 14:35 ` bugzilla-daemon
2022-06-08  8:45 ` bugzilla-daemon
2022-06-08  9:46   ` [Bug,209745] " bluez.test.bot
2022-06-10  9:58 ` [Bug 209745] " bugzilla-daemon
2022-06-10 16:37 ` bugzilla-daemon
2022-06-13  8:36 ` bugzilla-daemon
2022-06-15 22:00 ` bugzilla-daemon
2022-06-21  7:28 ` bugzilla-daemon
2022-06-21  9:05 ` bugzilla-daemon [this message]
2022-06-21  9:09 ` bugzilla-daemon
2022-06-21  9:10 ` bugzilla-daemon
2022-06-21 10:08 ` bugzilla-daemon
2022-07-14 17:42 ` bugzilla-daemon
2022-10-13 12:28 ` bugzilla-daemon
2022-10-17  2:36 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-209745-62941-NS7fxrZ9v5@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.