on: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 1884 F lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
Date: Mon Jan 26 20:34:17 2015
EcryptfsInUse: Yes
I have an HP Stream 11 and am also seeing the "stuck click" problem. I
built with the patch in comment #19 and can confirm that the problem is
now fixed. Also I believe bug #1394869 is about the same issue.
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Tags added: kernel-fixed-upstream-3.19-rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1398533
Title:
[HP Stream Notebook - 11-d010nr] clickpad malfunctions after
performing a cl
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 1884 F lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
Date: Mon Jan 26 20:34:17 2015
EcryptfsInUse: Yes
Hiberna
Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-29-generic 3.16.0-29.39
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 1884 F lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
Date: Mon Jan 26 20:34:17 2015
EcryptfsInUse
ith a dead-in-the-water
USB mouse, and with most of the USB devices no longer listed for lsusb.
My usb reset script (not mine - I found it online somewhere, and
modified it a bit to fit my situation) brought things back again and the
syslog entries look just like before... :
Nov 18 18:12:26 scott-
I just (yesterday?) installed Linux 4.8.0-29.31
"Release Tracking Bug
- LP: #1646194
* Yakkety update to v4.8.11 stable release (LP: #1645421)"
and for the first time since I installed Lubuntu 16.10, I can print, and have
the whole
page get printed!
This seems to have fixed the problem.
I also have this bug, which I filed for cups (since it first manifested with
several aborted print jobs, which I assumed somehow caused my USB mouse to stop
working)
See:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1637037
for details.
Summary:
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname
[By the way - until a fix reaches everybody, here is a script that I found
online and modified to fit my system...
The commented-out for statement is as the script was found.]
#!/bin/bash
if [[ $EUID != 0 ]] ; then
echo This must be run as root!
exit 1
fi
#for xhci in /sys/bus/pci/drivers/
"The fix is in the current 4.8 stable rc."
How will I know what exact kernel version (when it pops up in Update Manager)
is the first to include this fix?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Soon, I hope...
It will be nice to be able to print something, and not have it hang
somewhere in the middle of the page...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1630063
Title:
Public bug reported:
Just loading the latest updates
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-53-generic 3.13.0-53.89
ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.1
Public bug reported:
After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead
it turns off.
Journald output:
Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service:
Deactivated successfully.
Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3571] manager:
s
Upgrading to linux-image-
unsigned-6.2.1-060201-generic_6.2.1-060201.202302251141 did not fix the
issue.
Nor did rolling back to 5.17.0-1021-oem.
And along the way I found a log file which showed suspend working one
time with 5.17.0-1027-oem.
So now I'm not sure what changed to stop this working
Changing the BIOS Fastboot option to "Thorough" seems to have got it
working again. Not sure why this would be necessary now.
** Changed in: linux-signed-oem-5.17 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is su
801 - 816 of 816 matches
Mail list logo
