After i run apport-collect 1580029 and allow access to the browser. It seen i
can't run this command
Anyway the log of the apport-collect 1580029 is
.dpkg-query: no packages found matching linux
...
Traceback (most recent call last):
File "/usr/bin/apport-cli", line 370, in
if not
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1580029
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
@Stunts
I wonder if you had time and chance to test the possible fix. Let me
know because if it works then we could include it in the upcoming OTA
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.laun
Public bug reported:
Hello, i'm still on login loop after i upgrade kernel from 3.13.0-85 to
3.13.0-86 today with update notification application.
Note: It may affect with my Nvida Gtx 750 ti driver as i think.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You r
The computer is connected to two monitors to the motherboards DVI and VGA
outputs.
When I installed Ubuntu version 16.04, i had a problem - after every computer
restart VGA-monitor says "going to sleep" and darkens.
If I open "System Settings->Dysplays" and click on the monitor that is
connected
Just hit this same issue with nova-compute on Xenial and creating a
Xenial instance in nova. I worked around the issue with:
juju set-config nova-compute cpu-mode=host-passthrough
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: wily
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467
Title:
[Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
utopic-vy2yyy/linux-lts-
utopic-3
I'm grouping both bcmwl and broadcom-sta here. Because last time I
checked they were both based on the same upstream Broadcom code. So they
have the same bugs...
** Also affects: broadcom-sta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: broadcom-sta (Ubuntu)
Status:
*** This bug is a duplicate of bug 1578455 ***
https://bugs.launchpad.net/bugs/1578455
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1578455, so it is being marked as such. Please look
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1578455
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1579993
Title:
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
failed to build
Public bug reported:
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
failed to build
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic
Changing kernel to confirmed. This is a backport request for when that
patch lands upstream. It's still in discussions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "udev script"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579984/+attachment/4659578/+files/dell_dock.sh
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Statu
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1579984
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
I probably won't be able to followup with an upstream kernel report
until next week, due to various offline commitments. Will certainly look
into it at that point, however.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Nothing else required from you. It's the Ubuntu kernel team SRU process
from here on out. Joseph might be able to comment better on the expected
timing this will land in a new kernel version.
On Mon, May 9, 2016 at 7:15 PM Kyle Gochenour
wrote:
> That was it, thanks Mario:
> Linux yeti 4.4.0-2
For the record, if GRUB is setup to boot in text mode (so that the
graphical desktop does not come up), the keyboard is not working either:
the system books all the way to a tty prompt, then, despite the cursor
blinking the whole time (never stops blinking, like it does after a few
seconds for the
Dave - I wonder if https://bugs.launchpad.net/bugs/1579278 has any
bearing on your problem ?
--
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/1579917
Title:
Skylake processor with NVMe dri
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-lts-xenial (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because y
That was it, thanks Mario:
Linux yeti 4.4.0-21-generic #37~lp1577898 SMP Fri May 6 16:01:15 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
I can confirm that I can hotplug my Dell USB-C to ethernet adapter, as well as
my Nexus6p with a USB-C to USB-C cord as well.
So the patch is working for me as we
I'm also seeing this with 4.4:
$ uname -r -v -s
Linux 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016
--
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/1577099
Title:
[drm:inte
I have done a fresh Ubuntu 16.04 install and then I have installaed the
mainline kernel suggested, i.e. 4.6.0-040600rc6-generic.
I have tested all day long the machine and it seems there is no random
monitor shut-down anymore, nor "[drm:intel_cpu_fifo_underrun_irq_handler
[i915]] *ERROR*" in the k
You're still booted into the wrong one. His kernel would show a ~lp# in
the uname string. The one your are booted into is probably the one from the
archive that overwrote his on an apt update.
Install his again, don't do apt updates and try to boot into it.
On Mon, May 9, 2016, 18:05 Kyle Goc
Public bug reported:
I am receiving kernel OOPS while testing openvswitch with openflow to
redirect traffic to a proxy.
Things work fine if I run a slow tcp connection rate (10conn/s) on our
test framework.
As soon as I increase the tcp connection rate (1000 conn/s) the kernel
OOPS almost immedi
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1579943
Title:
Kernel OOPS
Status in linux p
Mario,
I found the issue. I am running 4.6.0-040600rc4-generic from testing in my bug
report. I had install jsalisbury's kernel but was not booting into it. I hit
GRUB on the reboot and booted into 4.4.0-21 which matches his kernel.
I get this now for uname -a:
Linux yeti 4.4.0-21-generic #37-Ub
For virtualbox you should modify Makefile under following subdirectories
only: boxdrv, vboxnetapd, vboxnetflt and vboxpci.
The fix in #19 should be complete, since I'm currently on vanilla kernel
4.6.0-rc7 compiled with similar tweak and all modules compiled with
mentioned patches and Nvidia, Virt
Ah thanks. So maybe /etc/init.d/ondemand should have something to
override or disable it (say DISABLE=1 in /etc/default/ondemand)?
Looking at it currently, it seems to prefer governors in this order -
interactive, ondemand, powersave. Even an option in
/etc/default/ondemand to specify the preferr
Kyle,
Can you confirm from 'uname -a' what output you have?
That will confirm if you are booted into jsalisbury's kernel.
On Mon, May 9, 2016 at 5:10 PM Kyle Gochenour
wrote:
> I have duplicate bug #1571859 and tried the kernel above from jsalisbury
> and it did not work for me. However there i
Unfortunately, I'm just not in a position to experiment with the kernels
right now. I've got too much on my plate and any disruption would be a real
problem at the moment...
L
On Mon, May 9, 2016 at 2:54 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for yo
Hi, did you try the grub options: acpi_osi=! acpi_backlight=native
Does it solve the fan issue?
--
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/1520519
Title:
ASUS ROG GL552 TouchPad not
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
I have duplicate bug #1571859 and tried the kernel above from jsalisbury and it
did not work for me. However there is a chance that I may just suck at dealing
with kernels though.
(I installed all the packages except for the Cloud Tools.)
--
You received this bug notification because you are a
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1579917
Title:
Skylake processor with NVMe dr
This exact bug happens all the time for me on calls for more than around 2min.
The Bluetooth connection fail also happens during dialling - often on the first
call after a connection is established.
The only way to re-establish a connection is to disable bluetooth and
then re-enable it, and the f
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
Public bug reported:
Reproducer
1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case with
an NVME drive.
2. run powertop, and switch to idle stats tab
3. do nothing. *(as in let the machine idle till the cores regularly reach low
power states.
4. Watch the watts fly. On my
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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/1555608
Well, now, before installing, I tried the CD drive and it seems to be
working perfectly. Should I just wait and see if it happens again before
upgrading?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Thanks, Joseph. Bug exists on mainline 4.6.0-040600rc7.201605081830.
In first test it completely failed to mount card, spaming with errors:
May 9 16:05:53 dev-laptop kernel: [ 103.547966] mmc0: error -110 whilst
initialising SD card
May 9 16:05:57 dev-laptop kernel: [ 107.655738] mmc0: error
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for track
Done. Thanks for instructions. Unfortunately, upstream kernel doesnt
help.
I have this bug since I switched to a new computer (Ubuntu 14.04). I
have already tested Ubuntu 15.10 and Fedora 23. Everywhere the same
issue. I reported this bug, because it started to be frustrating. Every
time when I wa
Same problem here with a Lenovo T520 and this NIC
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
(8086:1502)
with the official kernel 4.4.0-22-generic #39-Ubuntu
No interface after coldboot, error -3. Everything is fine after a
reboot.
--
You receiv
Thanks Tim!
--
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/1579205
Title:
CONFIG_NR_CPUS=256 is too low
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in
** Tags added: patch
--
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/1542939
Title:
system freeze after vt switching
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Sure, I can try that. But since all the updates I usually do are through
the Update manager, which do I install first - 'headers' or 'image' , or
does it matter as long as i don't reboot until they're both installed?
--
You received this bug notification because you are a member of Kernel
Package
** Tags added: kernel-bug-exists-upstream
** 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/1579542
Title:
My computer
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1571796
Title:
linux-lts-utopi
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
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/1571667
Title:
linux: 4.2.0-36.41 -propos
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1572755
Title:
linux-armadaxp: 3
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1572258
Title:
linux-lts-vivid:
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the 3.2.0-1480.106 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks a
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
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/1571718
Title:
linux: 3.13.0-86.130 -prop
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1572261
Title:
linux-lts-trust
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
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/1571694
Title:
linux: 3.19.0-59.65 -propo
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
--
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/1571853
Title:
linux: 3.2.0-102.142 -prop
Indeed, you need my changes to debian/zfsutils-linux.install as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1532198
Title:
[MIR] zfs-linux
Status in zfs-linux package in Ub
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Fix Released
** Changed in: linux-lts-vivid (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kerne
This bug was fixed in the package linux-lts-wily - 4.2.0-36.41~14.04.1
---
linux-lts-wily (4.2.0-36.41~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572212
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trac
This bug was fixed in the package linux-lts-trusty -
3.13.0-86.130~precise1
---
linux-lts-trusty (3.13.0-86.130~precise1) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572261
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious rele
Stephen, i have no idea where that info came from. It seems someone has
changed the title of my bug. When this happened or for what purpose i
don't know. I don't even know if that information is accurate. It seems
to match my processor though..
The original title of my bug was: [Bug 1575467] [NEW]
This bug was fixed in the package linux - 3.19.0-59.65
---
linux (3.19.0-59.65) vivid; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571694
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
- L
This bug was fixed in the package linux - 3.2.0-102.142
---
linux (3.2.0-102.142) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571853
[ Kamal Mostafa ]
* [debian] BugLink: close LP: bugs only for Launchpad urls
[ Upstream Kernel Changes ]
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux-lts-wily - 4.2.0-36.41~14.04.1
---
linux-lts-wily (4.2.0-36.41~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572212
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trac
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux-lts-vivid - 3.19.0-59.65~14.04.1
---
linux-lts-vivid (3.19.0-59.65~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572258
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of
This bug was fixed in the package linux-lts-trusty -
3.13.0-86.130~precise1
---
linux-lts-trusty (3.13.0-86.130~precise1) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572261
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious rele
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux - 4.2.0-36.41
---
linux (4.2.0-36.41) wily; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571667
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
- LP:
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux-lts-wily - 4.2.0-36.41~14.04.1
---
linux-lts-wily (4.2.0-36.41~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572212
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trac
This bug was fixed in the package linux - 3.19.0-59.65
---
linux (3.19.0-59.65) vivid; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571694
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
- L
This bug was fixed in the package linux - 4.2.0-36.41
---
linux (4.2.0-36.41) wily; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571667
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
- LP:
This bug was fixed in the package linux-lts-vivid - 3.19.0-59.65~14.04.1
---
linux-lts-vivid (3.19.0-59.65~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572258
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of
This bug was fixed in the package linux-lts-vivid - 3.19.0-59.65~14.04.1
---
linux-lts-vivid (3.19.0-59.65~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572258
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
This bug was fixed in the package linux - 4.2.0-36.41
---
linux (4.2.0-36.41) wily; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571667
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
- LP:
This bug was fixed in the package linux-lts-vivid - 3.19.0-59.65~14.04.1
---
linux-lts-vivid (3.19.0-59.65~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572258
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of
This bug was fixed in the package linux - 3.2.0-102.142
---
linux (3.2.0-102.142) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571853
[ Kamal Mostafa ]
* [debian] BugLink: close LP: bugs only for Launchpad urls
[ Upstream Kernel Changes ]
This bug was fixed in the package linux-lts-trusty -
3.13.0-86.130~precise1
---
linux-lts-trusty (3.13.0-86.130~precise1) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1572261
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious rele
This bug was fixed in the package linux - 3.2.0-102.142
---
linux (3.2.0-102.142) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571853
[ Kamal Mostafa ]
* [debian] BugLink: close LP: bugs only for Launchpad urls
[ Upstream Kernel Changes ]
This bug was fixed in the package linux-armadaxp - 3.2.0-1665.90
---
linux-armadaxp (3.2.0-1665.90) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1572755
* Rebase to Ubuntu-3.2.0-102.142
[ Ubuntu: 3.2.0-102.142 ]
* Release Tracking Bug
- LP: #15
This bug was fixed in the package linux - 3.13.0-86.130
---
linux (3.13.0-86.130) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1571718
[ Benjamin Tissoires ]
* SAUCE: Input: synaptics - handle spurious release of trackstick
buttons, again
1 - 100 of 305 matches
Mail list logo
