Things are much improved now on cosmic 18.04 ubuntu studio:-
/sys/class/power_supply/BAT0/capacity:100
/sys/class/power_supply/hid-34:88:5d:87:92:8c-battery/capacity:85
Linux 4.18.0-11-lowlatency #12-Ubuntu SMP PREEMPT Tue Oct 23 21:12:42
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[The mouse is OK
Oops! My post #56 should have said the other synaptics mouse is also OK
on 18.04.1 LTS (not 17.10). I also got the release of cosmic wrong - it
is 18.10, of course!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubun
I suspect I need to open a new bug for the ASUS docking station
(detachable bluetooth keyboard with touchpad) under 18.04.1 LTS.
This system is completely up to date, but it still reports 0% charge all
the time.
I checked the directory tree for /sys/class/power_supply/AC0 (the mouse
is blah/BAT0)
The system is now running 19.04 x64 desktop. The problem has not changed
in any obvious manner, although reporting of battery status for its
external logitech bluetooth mouse is now correct.
Ca anyone suggest how to perform further problem determination, or
perhaps even a circumvention. The 0% bat
Excellent news! The bluetooth dock battery status started working
properly a couple of weeks ago. I can't be sure which update fixed the
bug, but here is the latest system status:-
ubuntu 19.10 eoan Desktop
5.3.0-26-generic x86_64 kernel
Bluez-* 5.50-0ubuntu4
gnome-bluetooth 3.34.0-1
udev 242-
I have the same problem with a Logitech M337 mouse and the
4.15.0-22-lowlatency kernel on my Dell Inspiron 15 laptop.
I also with a different Logitech M337 on the 4.4.15.0-22-generic kernel
on an Asus Transformer T300 Chi. Its bluetooth docking station reports
zero battery, too.
All three bluetoo
On 04/06/18 11:57, Daniel van Vugt wrote:
> Brian, it sounds like you should like a new bug.
>
> This bug is about a regression specifically in kernel 4.15, whereas 4.14
> works.
Thanks for your quick reply, Daniel. Unfortunately, it has me confused!
Both of my systems /are/ already running kern
On 04/06/18 13:02, Daniel van Vugt wrote:
> In comment #38 the original reporter confirms this bug did not exist up
> to and including in kernel 4.14. It only exists in kernel 4.15 and
> later.
>
> So on that basis any bug that does exist in 4.14 and earlier kernels
> would not be a duplicate of t
Public bug reported:
After upgrading my laptop from 16.10 ubuntu studio to 17.04, no DNS
names could be resolved with either an ethernet or wifi connection.
Something as simple as "ping myOtherHost" failed...
The Zesty 17.04 release notes clearly state "The default DNS resolver is
now systemd-res
Same messages for me with 16.04 beta2, running with bluez 5.37-0ubuntu5
on 4.4.0-15-generic amd64 kernel. Running on Asus T300 CHI notepad with
bluetooth keyboard/touchpad docking unit. It pairs OK, but connection
comes up briefly and then drops again.
bluetoothctl log extract follows:
[CHG] Devic
Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was n
Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was n
I also true using an old bluetooth usb dongle. I used it on the asus
T300, but that made no difference. I also tried it on my dell 1558
laptop, with 16.04 (64-bit) and 15.10 (32-bit with bluez 5.35). The
16.04 test was basically the same as on the asus. The 15.10 test was
different in detail, but s
On 15/04/16 03:19, Laurent Bonnaud wrote:
>> All tests produced the "not enough handles" message from bluetoothd.
>> Is anyone successfully using bluetooth with these later ubuntu kernels?
>
> On both of my systems I get the "not enough handles" messages but I got BT to
> work for both my use case
bug creation dialogue did not save the correct package name - presumably
I didn't do something properly.
** Package changed: usb-creator (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubun
15 matches
Mail list logo
