A non-Ubuntu kernel doesn't have the required tracepoints and will
result in the following error.
ureadahead: Error while tracing: No such file or directory
If you're not running a stock Ubuntu kernel you will need a patch [1]
(worked on my 4.14 Debian kernel) or [2] (original patch).
Unfortunate
The following error could also indicate that your kernel doesn't have
the required tracepoints.
ureadahead: Error while tracing: No such file or directory
If you're not running a stock Ubuntu kernel you will need a patch [1]
(worked on my 4.14 Debian kernel). Unfortunately, these trace events
wil
This has been fixed and merged upstream in nm-applet/network-manager
1.4.2.
https://bugzilla.gnome.org/show_bug.cgi?id=763937#c14
Ubuntu 17.04 has 1.4.4. Is it possible to backport this to 16.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Does anyone know what the root cause of this digital in/out appearing?
Is it within ALSA or is there something wrong with the USB AudioControl
interface descriptor being returned by the USB audio device? I ask
because I have a custom USB audio device with this issue.
--
You received this bug noti
I'm curious what the root cause of this bug is because I have a custom
USB audio device with this issue. Is it within ALSA or is something
wrong with the USB audio device's AudioControl Interface descriptor?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
I added the keys sysfs attribute to gpio-keys-polled.c. Please try this
patch (should apply on ubuntu-linux 4.3).
diff --git a/drivers/input/keyboard/gpio_keys_polled.c
b/drivers/input/keyboard/gpio_keys_polled.c
index 11e77a9..3a8ee50 100644
--- a/drivers/input/keyboard/gpio_keys_polled.c
+++ b/
gpio-keys-polled: add sysfs bitmask to export supported keycodes
** Patch added: "gpio-keys-polled-sysfs-keys.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1347776/+attachment/4529893/+files/gpio-keys-polled-sysfs-keys.patch
--
You received this bug notification because you a
Public bug reported:
initramfs network booting by default fails after a fixed number of
attempts/timeout to configure the network. For example, in an automation
environment with heavy DHCP usage, a system will give up trying to get a
DHCP lease after 265 seconds. This will require manual intervent
8 matches
Mail list logo