Its just a shame that no one is interested in this bug. Debian Stretch
doesn't have this bug btw and bugs get fixed more quickly there ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchp
@xnox
sudo apt install dracut-core did not work for me.
In my case:
raid md1 was unmounted but raid md0 was not.
raid md0 was mounted to /
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad
Public bug reported:
Hi,
after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan
working. I get the following error:
hcitool lescan
Set scan parameters failed: Input/output error
Bluetooth hardware:
hci0: Type: Primary Bus: USB
BD Address: 04:EA:56:21:xx:xx ACL MTU:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347851/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.
apport information
** Tags added: apport-collected
** Description changed:
Hi,
after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan
working. I get the following error:
hcitool lescan
Set scan parameters failed: Input/output error
Bluetooth hardware:
hci
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347849/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347850/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347865/+files/CurrentDmesg.txt
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347848/+files/CurrentDmesg.tx
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347856/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://b
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347859/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347860/+files/rfkill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347861/+files/syslog.txt
** Attachment removed: "syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347861/+files/syslog.txt
--
You received this b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347858/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347855/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347857/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347853/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347863/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347854/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
h
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1870837/+attachment/5347852/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.
I tested the following mainline kernels:
Linux xxx 5.3.18-050318-generic #201912181133 SMP Wed Dec 18 16:36:09 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
root@xxx:~# hcitool lescan
Set scan parameters failed: Input/output error
root@xxx:~# uname -a
Linux xxx 4.15.18-041518-generic #201804190330 SMP
With current Ubuntu 18.04 installed on focal and the current bluez v5.48
(current Ubuntu 18.04 version):
I get the following error:
root@xxx:~# uname -a
Linux xxx 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
root@xxx:~# hcitool lescan
Could not open
On uname -a
Linux xxx 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux even with up to date focal bluez version the bluetooth
device isn't recognized:
dmesg | grep Bluetooth = empty output
The backup usb bluetooth dongle also doesn't work with this ker
I also think it's not a kernel issue since bluetoothctl is working and
able to find Bluetooth low energy devices.
Bluez Ubuntu 18.04 version with latest focal kernel also results in:
hcitool lescan
Set scan parameters failed: Input/output error
--
You received this bug notification because you a
After some more investigation I found out that the software I am using
is NOT using hcitool. It really seems to be another problem since the
custom software and the hcitool lescan command are throwing the same
error observed with btmon:
@ RAW Close: hcitool
Installed blueman for testing purpose (wasn't installed before): it is allowed
to perform these commands:
@ RAW Open: blueman-manager (privileged) version 2.22
{0x0004}
20:43:17.578682
@ RAW Close: blueman-m
The bug is still present for me with
ii isc-dhcp-server 4.4.1-2.1ubuntu4
amd64ISC DHCP server for automatic IP address assignment.
apparmor rules are up to date with:
owner @{PROC}/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
Bug still present in current Ubuntu 20.04 beta:
dmesg|grep accordingly
[ 63.817919] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream=
references a path below legacy directory /var/run/, updating
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update
the unit f
Executing "hcitool cmd 0x03 0x0003" made the error with hcitool disappear:
hcitool lescan
LE Scan ...
But hcitool does not seem to work as I can't find any ble devices.
btmon output after executing "hcitool cmd 0x03 0x0003 and hcitool lescan:
> HCI Event: Command Complete (0x0e) plen 4
After some time I am back to:
hcitool lescan
Set scan parameters failed: Input/output error
Issuing
hcitool cmd 0x03 0x0003
< HCI Command: ogf 0x03, ocf 0x0003, plen 0
> HCI Event: 0x0e plen 4
02 03 0C 00
helps again, but I still can't find any BLE devices with hcitool lescan.
Nevertheless the
It seems to me that the "normal" LE commands are broken and only the LE
Extended commands are working?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1870837
Title:
hcitool
Bluetoothctl and blueman are both using LE Extended commands and are
therefor working I think.
(btw: I would edit my comments if I could ...)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launc
So, my fault: It IS actually a kernel issue. I didn't install linux-
modules-extra-4.15.0-96-generic package when trying out Ubuntu 18.04
stock kernel on Ubuntu 20.04. After installing this package hcitool
lescan works flawlessly...
** Package changed: bluez (Ubuntu) => kernel-package (Ubuntu)
--
Public bug reported:
isc-dhcp-server crashing constantly (sometimes within seconds or minutes,
sometimes within hours) with the following error messages:
Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361:
INSIST(!so
New error log:
Apr 10 22:11:47 xxx dhcpd[3765]: Server starting service.
Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: peer moves from
normal to communications-interrupted
Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: I move from
startup to normal
Apr 10 22:11:47 x
My current workaround: downgrade isc-dhcp-server to 18.04 package
version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872106
Title:
isc-dhcp-server crashing constant
My current workaround: downgrade isc-dhcp-server to 18.04 package
version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
DHCP Cluster crashes after a few
My system is up to date with the newest package versions.
** Package changed: isc-dhcp (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872106
It seems to be still an apparmor problem:
[1863665.820588] audit: type=1400 audit(1588413129.073:171): apparmor="DENIED"
operation="open" profile="/usr/sbin/dhcpd"
name="/proc/sys/net/ipv4/ip_local_port_range" pid=38217 comm="dhcpd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[1863665.8209
After disabling apparmor, the dhcp server keeps crashing ...
** Package changed: apparmor (Ubuntu) => isc-dhcp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/18721
39 matches
Mail list logo
