As per https://patchwork.kernel.org/patch/10384111/ message from Bluez
mailing list, editing 97-hid2hci.rules as follows works around the new
uevents added to the kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
-ACTIO
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14,
so sticking with the old kernel that works for now.
Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail.
systemd-udevd has always consumed 100% whenever a udev rule fails (could be
argued that's also a bug b
Also occurs on Zesty installations that have been upgraded from Yakkety.
Unity8 fails to launch (classic black screen) and unity8.log shows the error:
"character conversion failed"
This is due to incorrect multiple versions of boost being present on the
system because they aren't removed when upg
Many thanks Martin.
Trawling through the linux-usb and distro kernel mailing list archives
shows that the kernel blocking problem has been around for some time and
discussed at length.
What it seems to boil down to is this:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/dri
So whether it be broken/missing libs or bad USB device enumeration
causing upowerd to be either not available or slow to start, it would
seem unity-settings-daemon could at least be improved to be robust
enough not to segfault if upowerd is not present.
In the meantime, I was able to solve the USB
One last thing...ice in comment #12 said:
"Some people say it has to do with a ASMedia USB Controller"
Have found that USB enumeration failure can cause a bottleneck in
systemd getting the upower.service unit to finally start.
You'll know if the system is hit with this as it'll be much slower to
Looks to be a race condition where the session (and so unity-settings-daemon)
is started before systemd has finished starting the upower.service unit.
u-s-d tries to query the state of power and segfaults when upowerd hasn't
finished initialising to be able respond.
>From syslog:
17:14:31 kernel
Bug still present in Xenial.
Creating symlinks as suggested in comment #2 has the unwanted side
effect of creating duplicate entries for KDE applications in the Search
and Applications lense.
So it would seem the proper fix would instead be for Unity to grab the
path of where the konsole.desktop
8 matches
Mail list logo
