Can't turn on Bluetooth after turning it off
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hey there!
I am encountering a bug in Bluetooth menu in drop down menu at top right corner.
Whenever i turn off my Bluetooth there is no option to turn on there. It shows two option turn off and Bluetooth setting. After I open setting and try to turn it on from there it doesn't turn on.
I need to restart the system to make it work.
Please fix this issue.
Thank You
Vipin Singh Negi
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSign
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 1 22:50:43 2020
InstallationDate: Installed on 2020-05-31 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_IN
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.6A
dmi.board.
dmi.board.name: 3564
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 21.46
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion g4 Notebook PC
dmi.product.sku: D7Z60PC#ACJ
dmi.product.
dmi.sys.vendor: Hewlett-Packard
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 48:D2:24:58:55:67 ACL MTU: 1022:8 SCO MTU: 183:5
DOWN
RX bytes:1957 acl:0 sco:0 events:90 errors:0
TX bytes:4974 acl:0 sco:0 commands:75 errors:0
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1738838, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.