** 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
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
@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
...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"
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"
Public bug reported:
Attempting to slide the "Connection" switch in the gui to connect a
bluetooth device fails initially -- the switch moves but "snaps back" by
itself immediately. Clicking on the switch flashes the "busy"
indicator momentarily, but the switch does not move. After a while,
Ok, the mis-directed output seems to be fixed with a kernel 5.2.
With the stock 5.0.0-21-generic, disconnecting BT in the Ubuntu gui does
not actually disconnect immediately. Instead, the disconnect happens
when BT is turned ON again in the gui!
(based on my BT headset's synthesized
Public bug reported:
Bluetooth headset stopped working after upgrading to 19.04. Worked
perfectly with 18.10.
Now, when a BT headset is connected the volume-control widget (seen via
the speaker icon in the upper-right corner) displays a headset icon and
a volume slider, but the slider has NO
The error message occurs during any normal kernel update, not just during
autoremove.
I can reproduce it at will with "sudo apt-get install --reinstall
linux-image-4.2.0-29-generic" (or whatever the latest version is).
I changed the bug title accordingly
** Description changed:
- Running
I used strace on apt-get and it attempted to access the following non-
existent files:
/var/lib/dkms/vboxhost/5.0.9/source/dkms.conf
/var/tmp/mkinitramfs_OcRxJk/etc/modprobe.d/dkms.conf
The file /var/lib/dkms/vboxhost/5.0.9/build/dkms.conf DOES exist, but
was NOT accessed.
The file
Public bug reported:
Running "apt-get autoremove" after a kernel update produces messages
like this:
run-parts: executing /etc/kernel/postinst.d/dkms 4.2.0-19-generic
/boot/vmlinuz-4.2.0-19-generic
Error! Could not locate dkms.conf file.
File: does not exist.
But dkms seems to be
Does not work for me.
Running 14.10 with utopic-proposed enabled; an update installed gnome-bluetooth
3.8.2.1-0ubuntu9 amd64
Several errors were logged. It looks like an error occurs when starting
discovery, before even attempting to pair with a device. And after
attempting to pair, the
12 matches
Mail list logo
