Christopher, please open a new bug for what you experience by running:
ubuntu-bug gnome-shell
This bug should stay closed while the original reporter hasn't provided
the requested info.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
Still an issue in the latest Ubuntu 20.04 release.
User winds up having to click the toggle over and over again while it
stubbornly snaps back.
Replicated on Many different machines with different hardware.
Is there anyone who can not replicate this bug?
** Changed in: bluez (Ubuntu)
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838227
OK then, in the VM please open a Terminal (Ctrl+Alt+T) and run:
rfkill > rfkill.txt
and then attach the file 'rfkill.txt' here.
Alternatively run:
rfkill
and just take a screenshot.
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification
Please also run this in both the VM and on the host, and send us both
outputs:
lsusb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838227
Title:
Bluetooth "Connection switch" snaps back by
Well, I see the problem also on real hardware, but it's harder to
reproduce. In any case, I don't want to install a non-standard kernel
there, so it is mixed up with the other problems with the 5.0 kernel.
However, the VM *does* indeed have bluetooth. Virtualbox allows VMs to
access any USB
** Attachment added: "newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279955/+files/newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt
--
You received this bug notification because you are a member of
Thanks. The common factor still seems to be:
Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: Unable to get Headset
Voice gateway SDP record: Device or resource busy
Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: connect error: Device
or resource busy (16)
which is the same
Hmm, you reported this bug from a virtual machine which doesn't seem to
have any Bluetooth hardware, so actually I would expect the switch to
not work.
Please submit a new bug from a real machine if that's where you are
seeing the problem.
** Changed in: bluez (Ubuntu)
Status: Incomplete
...and here is a smaller log covering only a single attempt to slide the
connection switch to the right (the switch snapped back immediately by
itself)
** Attachment added: "newlog_SingleTry_2019_07_29.txt"
@Daniel Here you go (newlog_2019_07_29.txt). The log covers only the
time while I tried to connect to the headset (took several tries before
the switch switched; there are maybe a dozen mouse actions during that
time).
There are many message like this:
org.gnome.Shell.desktop[1585]: Window
Thanks for the log file(s). Unfortunately that last one covers several
days.
Could you please record the system log for the short period of time
while reproducing the bug again?
1. In a terminal window run:
journalctl -f > newlog.txt
2. Reproduce the bug again.
3. Ctrl-C in the terminal
Thanks for the log file(s). Unfortunately that last one covers several
days.
Could you please record the system log for the short period of time
while reproducing the bug again?
1. In a terminal window run:
journalctl -f > newlog.log
2. Reproduce the bug again.
3. Ctrl-C in the terminal
I rebooted before submitting this bug report using ubuntu-bug, so syslog
is probably the wrong one. I'll attach the previous one (syslog.1) which
I think covers the test demonstrated in the video (and several earlier
attempts).
** Attachment added: "syslog.1"
14 matches
Mail list logo
