[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Just want to update this bug - I have not found a fix for this. Instead
I've been relying on the Logitech universal receiver which is working
great in my experience.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
New
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
New
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Thank you Daniel! Over the week I upgraded my laptop to Mantic, so can
no longer test for Jammy.
I still can't discover my logitech mice in Mantic, so maybe still the
same situation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in `bluetoothctl scan
on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-03-06 (242 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: bluez 5.68-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/usr/bin/zsh
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-10-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
+ UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/18/2023
+ dmi.bios.release: 1.58
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET75W (1.58 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QDUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.25
+ dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
+ dmi.product.family: ThinkPad X1 Carbon 7th
+ dmi.product.name: 20QDUS
+ dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
+ dmi.product.version: ThinkPad X1 Carbon 7th
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+ hci0:Type: Primary Bus: USB
+ BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
+ UP RUNNING PSCAN ISCAN INQUIRY
+ RX bytes:21473 acl:0 sco:0 events:2871 errors:0
+ TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
+ mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715722/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2040657 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: jammy ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: Incomplete Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
I am able to connect with the unifying receiver which is good enough for now. It'd still be nice for regular bluetooth to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Actually after opening this bug I decided to try my MX master 3S with bluetooth mode and that's not detected either. I also tried a pair of airpods and those are not seen. the weird part is that I am actively using some samsung galaxy buds with this laptop via bluetooth and they work. So perhaps there's something generally wrong with bluetooth discovery on my laptop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2040657 Title: bluez does not detect Logitech Pebble M350, no option to connect Status in bluez package in Ubuntu: New Bug description: I lost the proprietary USB dongle and decided I wanted to try bluetooth with this particular mouse. I am able to connect with bluetooth on Windows 11, but the device doesn't even show up in `bluetoothctl scan on`. This is seen on Jammy with bluez 5.64-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
