** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1552378
Title:
Xenial doesn't see all cores nor usb network don
Public bug reported:
Since the bluez5 transition my mako has not been able to pair with the
radio in my 2014 Subaru Forester. When the radio is put into pairing
mode the phone sees the CAR_M_MEDIA device, but when I click "connect"
the radio immediately shows "failed" and no PIN prompt is shown on
** Attachment added: "system-settings log showing some potentially interesting
errors"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4586975/+files/application-legacy-ubuntu-system-settings-.log
** Also affects: canonical-devices-system-image
Importance: Undecide
** Attachment added: "kernel/initrd pair with kernel/drivers/net/usb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552378/+attachment/4587013/+files/test-kernel.txz
** Changed in: maas-images
Status: New => Triaged
** Changed in: maas-images
Importance: Undecided => Medium
the lack of usb nic is because the xenial image does not have a "full
kernel" inside it . 14.04 maas images had linux-generic installed. So
if you were commissioning with hwe-t (ie, you had no need for a newer
hwe kernel) then your commissioning would get all the drivers in linux-
generic at its
Also, the kernel team would probably appreciate you running 'apport-
collect 1552378'
--
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/1552378
Title:
Xenial doesn't see all cores nor usb n
It is intentional, as the bq-aquaris channel includes things like the
HERE AGPS service.
My BT keyboard, mouse, and headset all work so it's something to do with
the HFP changes that came with bluez5 I have to assume, since before the
switch I could pair with the car just fine.
--
You received t
We really need to understand what is creating this file because
apparently in live build, its not the installation of a kernel.
--
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/1536810
Title
** Description changed:
Hi, this failure for kernel package installation occured inside a maas image
(lp:maas-images) build process.
The failure log ends like this:
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-gen
Public bug reported:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the underlying target dom0 (migrating a
64-bit domU involves a 1GB malloc in dom0, as well as a lot of
unnecessary work).
I
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1542941
Title:
Regression: problems migrating recent wily/vivid Xen VM
That's the patch which *introduces* the regression.
The missing one is 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d.
--
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/1542941
Title:
Regression
Apologies for the confusion; I had the right commit ID but pasted the
wrong description. Now fixed, I think!
** Description changed:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the
Public bug reported:
Hi, this failure for kernel package installation occured inside a maas image
(lp:maas-images) build process.
The failure log ends like this:
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-generic (4.3.0-7.1
For full disclosure, this is in a "cross" build environment (qemu-static).
this works for other versions of ubuntu and has worked for xenial in the past.
the error messages seem to indicate 'update-initramfs' was deferred, but
the the postinst tried to copy it into place even though it wasnt there
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1536810
Title:
kernel install failed /bin/cp: cannot stat
‘/boot/ini
what provides (or should create) /etc/kernel.conf ?
--
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/1536810
Title:
kernel install failed /bin/cp: cannot stat
‘/boot/initrd.img-4.3.0-7-g
** Attachment added: "script reproducing problem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4556461/+files/reproduce.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
I've checked, and the file exists. the content is
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
For reference, show-kernel-img-conf.
this downloads cloud images and extracts the questioned file.
Note, there is a change in this file from wily to xenial, but the change is in
place for all arch, and i'm only seeing these build failures in arm64 and armhf.
== wily armhf [wily-server-cloudimg-a
Note, there are 2 changes fom wily to xenial in the content of that file:
a.) for arches other than amd64, we gain the 'link_in_boot = yes'
b.) there is a case change for the 'do_symlinks' setting from wily ('Yes') to
xenial ('yes')
--
You received this bug notification because you are a membe
It seems to be 'a' that causes the failure.
If i remove 'link_in_boot' then it works.
I've committed a change to maas-iamges to work around this at least temporarily
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/268
--
You received this bug notifica
It'd be nice to track down why images have this change from wily in
them, especially since it is not helpful.
--
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/1536810
Title:
kernel install
"the kernel at least created the configuration".
I don't know where the file came from, but that is the file that is in
official ubuntu cloud images, built by livefs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
ok, so it is /lib/modules-load.d/open-iscsi.conf that has 'ib_iser' in
it.
ib_iser per modinfo "iSER (iSCSI Extensions for RDMA) Datamover".
per depmod on full linux-image-extra system:
kernel/drivers/infiniband/ulp/iser/ib_iser.ko:
kernel/drivers/infiniband/core/rdma_cm.ko
kernel/drivers/infi
So, some conversation with infinity at
http://irclogs.ubuntu.com/2016/04/07/%23ubuntu-devel.html .
All of ib_iser's deps are already in linux-generic
(http://paste.ubuntu.com/15670921/)
So we might as well move that module also.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
**
I tried to pair today using bluetoothctl but all I got back was
Failed to pair: org.bluez.Error.AuthenticationRejected
and the same "failed" message on the radio display.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
h
** Branch linked: lp:~ssweeny/bluez/snappy-interface
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1560094
Title:
Starting bluez service is denied
Status in bluez package in Ubuntu:
Still didn't work for me.
** Attachment added: "syslog part containing pairing attempt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640867/+files/syslog-snippet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Attachment added: "ubuntu-system-settings log"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640868/+files/application-legacy-ubuntu-system-settings-.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bl
Here's the syslog snippet from when I tried pairing using bluetoothctl
** Attachment added: "syslog part containing pairing attempt using bluetoothctl"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4641441/+files/syslog-snippet-bluetoothctl
--
You received this bug
** Attachment added: "hcidump of a pairing attempt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4643207/+files/hcidump-hr.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
Would someone mind explaining, please, why this remote code execution
vulnerability was only just now fixed in precise despite being fixed
upstream in January?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https
In reply to Tim Chen (#27):
I have installed the bluez4-ssp as instructed. It works, however, there
is some weirdness. When I "Set up new device" and then select the K810
keyboard in the list and press the "Continue" button, it briefly shows
one 6 digit PIN number before showing the second one.
W
This is on the sync blacklist for Ubuntu with the rationale:
syncpackage: libmpc # jdstrand; orphaned with binaries provided in libmpcdec
(LP :#540019)
Has that changed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libmpc in Ubuntu
I have reproduced this on a Macbook pro ( 10,1 ) with
Linux scottlinmacbook 3.14.1-031401-generic #201404141220 SMP Mon Apr 14
16:21:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
I'm running kubuntu and have never had RESUME work once. SUSPEND seems
to work, but RESUME fails 100% of the time. I c
*** This bug is a duplicate of bug 1297955 ***
https://bugs.launchpad.net/bugs/1297955
I can confirm this on a Macbook pro ( 10,1 ) running both:
Linux scottlinmacbook 3.14.1-031401-generic #201404141220 SMP Mon Apr 14
16:21:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
and 3.13
--
You receiv
For those still having trouble with this, I just got mine working by
merging the ArchLinux cros-haswell-modules.sh script with the Ubuntu one
(just one line that I transferred from one script to another which
contained the proper patch).
Here's my post and the pastebin of the script:
http://scottc
** Attachment added: "sudo dmi-decode > dmi-decode-x120e.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+attachment/4091139/+files/dmi-decode-x120e.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
same problem reproduces on live-ISO made from official 14.04 amd64
media.
** Description changed:
- fresh install of 14.04 on x120e.
- resume from suspend fails every time. I have to long-press the power button
and then turning it back on doesn't post to BIOS. To recover, I have to pull
the
verified this exists in linux-image-3.15.0-031500rc1-generic:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I just booted into saucy 3.11 and verified i have the issue.
linux-image-3.11.0-19-generic
I know that this did not exist before upgrade from saucy, so that would seem to
imply that kernel is not [entirely] at fault.
Given the fact that the hang requires me to pullt he battery and screen is left
regarding bios, and just to provide some information.
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/8fuj10uc.txt
has the changelog of the bios.
1.17 is currently the latest. Heres the last 4 changelog entries:
<1.17>
BIOS: 1.17 / ECP: 1.10
- (New) Updated CompuTrace ROM.
<1.16>
BIO
** Tags added: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1188092
Title:
[Feature] WiFi support in Stone Peak
Status in intel:
Fix Committed
Status i
** Attachment added: "trace from 3.13.0-8-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4060945/+files/wolfe-02-kernel-trace.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060977/+files/IwConfig.txt
--
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/13
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
We've seen this happen twice now on ppc64el guests that are probably
under load. I don't have a lot of the details on what was going on when
they failed, but I have the stack traces.
[101168.
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060973/+files/BootDmesg.txt
--
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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060975/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060982/+files/UdevLog.txt
--
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/1301
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060980/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060979/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060981/+files/UdevDb.txt
--
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/1301496
** Attachment added: "trace from 3.13.0-19-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4060946/+files/wolfe-01-kernel-trace.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1301496/+attachment/4060978/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
We've seen this happen twice now on ppc64el guests that are probably
under load. I don't have a lot of the details on what was going on when
they failed, but I have the stack traces.
[101168.836780] Unable to handle kernel paging request for data at address
0x00010001
[1011
Øyvind Stegard, I have been experiencing the same issues to those in #43
with the same laptop. See here for a report I filed a few months ago:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272624
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Summary changed:
- [Dell Latitude E7440] 14.04 Touchpad not as smooth as Win7
+ [Dell Latitude E7440] 14.04 Touchpad causings mouse pointer to spuriously
jumps around
** Summary changed:
- [Dell Latitude E7440] 14.04 Touchpad causings mouse pointer to spuriously
jumps around
+ [Dell Latitud
x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 2284 F pulseaudio
Date: Wed Apr 9 07
amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 2284 F pulseaudio
Date: Wed Apr 9 07:53:51 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=400a4f7f-644a-451a-abaa-9ed26f4
/controlC0: scott 2284 F pulseaudio
Date: Wed Apr 9 07:53:51 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=400a4f7f-644a-451a-abaa-9ed26f4c04b1
InstallationDate: Installed on 2014-04-04 (4 days ago)
InstallationMedia
regarding stack 4k page kernel, this just happened on wolfe-02. running (I
believe) a 4k page kernel.
$ grep CONFIG_PPC.*.*PAGES /boot/config-3.13.0-8-generic
CONFIG_PPC_4K_PAGES=y
# CONFIG_PPC_64K_PAGES is not set
wolfe-02 login: [241848.101690] Unable to handle kernel paging request for data
Public bug reported:
fresh install of 14.04 on x120e.
resume from suspend fails every time. I have to long-press the power button
and then turning it back on doesn't post to BIOS. To recover, I have to pull
the battery and power back on.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: l
This is regression for me from 13.10, but in addition to re-install I
also replaced disk with an SSD.
--
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/1309112
Title:
x120e does not resume
Attaching /var/crash/susres.2014-04-17_12:45:58.004375.crash
** Attachment added: "susres.2014-04-17_12:45:58.004375.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+attachment/4086387/+files/susres.2014-04-17_12%3A45%3A58.004375.crash
--
You received this bug notificatio
I know this is for the touchscreen, but for the last beta wifi was
broken. Seems better with some updates, but not yet on final 14.04. Had
to install Ubuntu to hdd, as x64 uefi USB sticks would NOT auto boot. Now
get red secure boot warning every boot. Not Ubuntus issue. Posting to
forum ton
I have also confirmed that the current daily image (3/22/2014) was able to
boot and work with the following hardware:
touchscreen
wifi
dell wireless keyboard (unified)
dell wireless mouse (unified)
A "full install" of Ubuntu TT x64 on a USB stick will be tested later this
week. FYI, it will also
For convenience, attaching an example 'core.img'
from a trusty system at /boot/grub/i386-pc/core.img
** Attachment added: "core.img: example multiboot file that wont load"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1297316/+attachment/4042857/+files/core.img
--
You received
posted upstream at
http://lists.infradead.org/pipermail/kexec/2014-March/011346.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1297316
Title:
kexec doesn't load multiboot imag
Public bug reported:
kexec explictly (in --help and man page) reports to support multiboot
format images. That doesn't work for at least some subset of seemingly
proper multiboot images. For some context, the goal essentially the
same as discussed at [1].
mbchk is from 'multiboot' package (buil
** Summary changed:
- kexec doesn't load multiboot images
+ kexec doesn't load non-elf multiboot images
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1297316
Title:
kexec doesn't
** Changed in: kexec-tools (Ubuntu)
Status: New => Confirmed
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/b
This is a well known issue with Intel WiFi adapters (on both Linux and
Windows).
The only reliable "workaround" I've found is to disable 802.11n:
1. Open terminal.
2. sudo vi /etc/modprobe.d/iwlwifi-disable11n.conf
3. Add this line: options iwlwifi 11n_disable=1
4. Save and restart.
I've had thi
Is this still an issue? I'm happy to file a new bug report if you could
tell me what you mean by an "Ubuntu repository kernel".
Would it be helpful if I sent a report from a USB live instance of a
14.04 daily image?
--
You received this bug notification because you are a member of Kernel
Packag
Public bug reported:
This bug report has been produced to help improve the touchpad on a Dell
Latitude E7440 on Ubuntu 14.04 alpha.
However, from the live usb the touchpad seems quite smooth compared to
ubuntu 13.10... so this may already be fixed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Pa
I've produced a bug report here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272624
The touchpad doesn't seems to jerk now in Ubuntu 14.04 alpha.
(as an aside, the wifi on/off switch and sound now also both work out-
of-the-box)
--
You received this bug notification because you are a
Christopher, I've just tried the live image again and the cursor still
jumps/jerks around a little more than I would like. It is however
better than in 13.10 (but not as smooth as Windows 7)
I would therefore suggest that this bug report gets left open for now
until others can confirm the bug.
-
** Description changed:
This bug report has been produced to help improve the touchpad on a Dell
Latitude E7440 on Ubuntu 14.04 alpha.
- However, from the live usb the touchpad seems quite smooth compared to
- ubuntu 13.10... so this may already be fixed.
+ From the live usb the touchpad se
following up on #32, I may have been a little premature the mouse is
still a little jerky, but better than Ubuntu 13.10. However, it could
still do with some tweaking to be as smooth as Windows 7
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Christopher M. Penalver, I have just installed and rebooted to test the
following (below) and found that the bug still exists.
linux-image-3.14.0-031400rc4-generic_3.14.0-031400rc4.201402232235_amd64.deb
linux-headers-3.14.0-031400rc4-generic_3.14.0-031400rc4.201402232235_amd64.deb
** Tags added:
gnature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: scott 1915 F pulseaudio
/dev/snd/controlC0: scott 1915 F pulsea
It might be a reasonable time to take a look at stuff that should be in
-virtual.
I'd suggest that anything named "virtio" should be in -virtual.
I also notice
/lib/modules/3.13.0-13-generic/kernel/drivers/char/hw_random/virtio-rng.ko
that is in linux-image-extra-3.13.0-13-generic .
Can we have
Sorry for the huge delay in a response. I am obtaining the iso now. I
will be able to test it sometime next week. Does this image version
function as a live CD, as that will be my requirement for testing. I
cannot install it.
On Tue, Feb 18, 2014 at 10:49 AM, Joseph Salisbury <
joseph.salisb
Here is the output for 14.04 for synclient:
Parameter settings:
LeftEdge= 300
RightEdge = 1700
TopEdge = 210
BottomEdge = 1190
FingerLow = 12
FingerHigh = 15
MaxTapTime =
Following #6, the synclient output for ubuntu 13.10 differs for the
following options (ubuntu 14.04 output is in brackets)
RTCornerButton = 0 (2)
RBCornerButton = 0 (3)
LTCornerButton = 0
LBCornerButton = 0
TapButton1 = 0
The main problem seems to be when I place a second finger close to my
first finger causing the cursor to jump and jerk across the screen
(i.e., disappers and reappears in any other part of the screen). I have
tried to alter values in synclient to reduce this but I haven't had much
luck.
I've comp
Allan, in syslog I see the following...
Jan 27 18:19:29 oort kernel: [ 206.716178] psmouse serio1: GlidePoint at
isa0060/serio1/input0 lost sync at byte 1
Jan 27 18:19:29 oort kernel: [ 206.717133] psmouse serio1: GlidePoint at
isa0060/serio1/input0 lost sync at byte 1
Jan 27 18:19:29 oort ker
*** This bug is a duplicate of bug 1265436 ***
https://bugs.launchpad.net/bugs/1265436
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
u
The verification of the Stable Release Update for mikutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In the
event that you encounter a
Public bug reported:
Suspend no longer works on my laptop running Trusty. It will just blank
the screen for a few seconds then come back up to the unlock prompt.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-8-generic 3.13.0-8.28
ProcVersionSignature: Ubuntu 3.13
I have now installed the latest daily image of Ubuntu 14.04 as the main
install to help with testing before the final release.
The mouse cursor is still jumpy as described above. If another bug
report or further information would be useful at anytime feel free to
let me know.
--
You received th
/vmlinuz-3.13.0-8-generic]
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: scott 1915 F pulseaudio
/dev/snd/controlC0
Hi Christopher, this was also a problem in Ubuntu 13.10.
--
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/1272624
Title:
[Dell Latitude E7440] 14.04 Touchpad not as smooth as Win7
Status
Christopher, I have not personally tested on a release prior to Saucy
but according to comment #15 in bug 1258837 the touchpad bug (if it is
the same) didn't seem to exhibit itself in earlier kernel versions used
in 12.04
--
You received this bug notification because you are a member of Kernel
Pa
Christopher M. Penalver, in the live USB of 12.04.0 the two-finger
scrolling can not be activated under Settings-->Mouse. The problem was
not reproducable but I put that down to the OS not recognising the
second finger.
Edward-douse, I tried the newest version of ElementaryOS and the results
were
Sorry it took so long, but I reproduced the bug with the upstream
kernel.
** Tags added: kernel-bug-exists-upstream
--
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/1280304
Title:
[System
3.13.0-23-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1355196
Title:
unity crashes on login, compiz cpu and memory in
Chris seems to have correctly identified the issue.
I tried reverting the xserver-xorg-video-intel to previous versions, but it had
no affect.
I rebooted into an older kernel and i can still use compiz/unity.
3.16.0-6-generic : works
3.16.0-7-generic : fails
3.16.0-8-generic: fails
** Summar
** Description changed:
Recent upgrade and reboot/re-login left me with a generally unusable
compiz/unity.
On login, the desktop icons move back and forth several times, I believe this
correlates with ~/.xesssion-errors 'unity main process ended' messages like:
-
- upstart: gnome-keyring ma
301 - 400 of 816 matches
Mail list logo
