No, this problem existed in earlier kernels also. I've used 16.04 before - and
it was the same there.
I've also tested it with the latest upstream kernel and it still exists.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
dmidecode
** Attachment added: "dmidecode"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637702/+attachment/4769255/+files/dmidecode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637702
** Summary changed:
- [DNS Travel 0157253] Touchpad does not work (i8042.noloop=1 as a workaround)
+ [DNS Travel 0157253 / X300V] Touchpad does not work (i8042.noloop=1 as a
workaround)
** Description changed:
- The touchpad of my local-branded notebook is not working (cursor is not
- moving,
Public bug reported:
The touchpad of my local-branded X300V-based notebook (DNS Travel
0157253) is not working (cursor is not moving, buttons do not function)
There is a WORKAROUND: adding i8042.noloop=1 to GRUB_CMDLINE_LINUX in
/etc/default/grub
sudo nano /etc/default/grub
cat /proc/bus/input/devices
** Attachment added: "devices"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637702/+attachment/4769232/+files/devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do any of the above solutions work for 16.10? Or currently there's no
working bluetooth driver for Ralink RT3290 in 16.04?
My 'lspci -v' for 3290 lines: http://paste.ubuntu.com/16311034/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've had the same problem with daily Maverick after running sudo
tasksel install lamp-server: tasksel: aptitude failed (100).
I tried to follow above instruction and run sudo apt-get update.
The last line of response was:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a'
Eric Hammond: Thank you. Commenting on the closed ticked turned out to
be the best way to open the new, right and detailed one :)
--
ec2-fetch-credentials lists ubuntu user in root authorized_keys even if
ec2-config.cfg specifies another
https://bugs.launchpad.net/bugs/506981
You received this
I second the idea of adding the quotes to the username. The present
warning makes very little sense to the person unfamiliar with Linux,
like me.
Please login as the ubuntu user rather than root user.
I spend a good half an hour trying to find what should I do to login to the
system.
I'm sure
