Public bug reported:
After the kernel upgrade from 3.13.0-91-generic to 3.13.0-92-generic,
the kernel modules I built for the MEDIATEK Corp. MT7630e 802 in my
laptop wont load anymore (hence no wifi), but they still do when using
the startup menu to boot 3.13.0-91-generic.
Problematic kernel vers
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
http://pe
Thanks Rocko (my fellow Perthian?). It seems you're right the modeset
driver is just not /inventing/ the fake modes you desire.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- mod
no difference on that particular older kernel. I'm testing 4.7.0 generic
kernel, as that just exited rc7. I have no specific reason to believe
that I will have different results with this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc2
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.7
needs-reverse-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
sasha1024, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
** Changed in: linux
Evy Karavatselou, would the latest 4.7 (not the rc's) allow a test? If
not, could you please advise on 4.7-rc5/rc6?
** Tags removed: kernel-bug-exists-upstream-4.5
** Tags added: kernel-bug-exists-upstream-4.7-rc5
** Tags removed: kernel-bug-exists-upstream-4.7-rc5
** Tags added: kernel-bug-exist
Hi Seth, for 16.04 "apt install" works on local *.deb files, invoking
dpkg ion the process. I have previously installed dozens of packages
from debs via dpkg -i, and from what I've seen there's no difference
between that and apt install on 16.04. I also confirmed that 4.7 was
installed via uname -r
** Changed in: xorg-server (Debian)
Status: Unknown => 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/1606103
Title:
modeset driver does not detect all screen resolutions
Sta
The bisect reported the following as the first bad commit:
commit 1302fcf0d03e6ea74846c7fee14736306ab2ce4b
Author: Bjorn Helgaas
Date: Sat Aug 30 07:23:01 2014 -0600
PCI: Configure *all* devices, not just hot-added ones
I built a Xenial test kernel with a revert of this commit.
The test
Is there a way to obtain a vmlinux image for the upstream kernel as
built by ubuntu (without having to compile locally) so that I can
compare the disassemblies of the ftrace_stub ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
I tried with the upstream kernel :
nborisov@fisk:~$ uname -a
Linux fisk 4.7.0-040700-generic #201607241632 SMP Sun Jul 24 20:34:30 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
In the meantime I managed to find a sequence which can trigger this 100%
of the time on the ubuntu kernel. The following comm
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1591704
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
With "sudo pm-suspend" the system quickly auto-resume (nearly nothing happen).
No terminal output.
--
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/1606178
Title:
Can't suspend to ram, sin
I'll test 3.5 kernel (suspend working with ubuntu12.04) for fun.
Please tell me if I can do something to help to resolve this issue, I'm
still running 12.04 just because of that!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Note: for most of kernels tested, the suspend seem to work, the screen
turn blank and cpu fan seem off, but the CD drive make a noise (same as
when I boot) and then the system resume (with certain kernels, there is
no way to resume).
With 4.7:
the login screen is a little strange: the mouse cursor
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/1606384
Title:
Ubuntu does not boot with syst
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/1584557
Title:
Seagate external drive causes
Public bug reported:
Ubuntu does not boot with systemd, it boots with upstart choice in grub.
Workaround - alt+f1 during start and then start lightdm manually.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
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/1584557
Title:
Seagate external drive causes SCSI bus resets when UA
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS clie
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: acce
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
*** This bug is a duplicate of bug 1588946 ***
https://bugs.launchpad.net/bugs/1588946
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: a
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
*** This bug is a duplicate of bug 1605709 ***
https://bugs.launchpad.net/bugs/1605709
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: a
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (na
You have been subscribed to a public bug:
Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
continuous SCSI bus resets by default. As a workaround, disabling UAS
causes the device to work fine.
To disable UAS, I created a file in /etc/modprobe.d with the following contents:
opt
Not sure how to submit the SRU request. The page linked above talks
about verifying patches, and there are none attached to this bug.
--
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/1606030
So the panic does not happen anymore with the 4.4.0-31 kernel?
Can you open a new and separate bug report for your wireless 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/1605731
T
Not message in kernel 4.7
** Attachment added: "dmesg_4.7.0-040700-lowlatency"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605782/+attachment/4707325/+files/dmesg_4.7.0-040700-lowlatency
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a m
This does appear to be an Ubuntu specific kernel. I'll build an Ubuntu
kernel based on 4.0 and post a link to it for testing.
--
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/1603810
Title:
Ahh, yes it was. Comment 8 is a duplicate request, sorry about that.
--
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/1603810
Title:
Ubuntu turns monitor permanently off during boot
Stat
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
I removed that kernel and installed it again. This time, it didn't
panic, but Wireless connection does not work.
--
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/1605731
Title:
Kernel 4.4.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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: Incomplete => Triaged
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status:
Can you submit an SRU request[0] to the kernel team mailing list:
kernel-t...@lists.ubuntu.com
[0] https://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received thi
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0
Wasn't testing with 3.16 and 3.19 ubuntu patched kernels enough to disprove
the grub theory?
Jason
On Mon, Jul 25, 2016 at 1:44 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Can you see if the bug still happens when booting a Trusty kernel on the
> Xenial system? This can be d
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1605782
Title:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CP
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Also, can you grab a screen shot or take a digital picture of the panic?
Then attach it to the bug for review.
--
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/1605731
Title:
Kernel 4.4.0-
This version is broken.
--
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/1571798
Title:
Broadwell ECRC Support missing in Ubuntu
Status in linux package in Ubuntu:
In Progress
Status in
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1604814
Title:
Newest kernel update disables wireless and touchpad
Statu
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in:
Can you see if the bug still happens when booting a Trusty kernel on the
Xenial system? This can be down by downloading the kernel from:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/10184623
You will need to install both the linux-image and linux-image-extra .deb
pack
I built the next test kernel, up to the following commit:
1302fcf0d03e6ea74846c7fee14736306ab2ce4b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1571798
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I've managed to source a slightly-used QL-570 for a more reasonable
price, along with (apparently) five rolls of labels. That should be
arriving "soon-ish".
I'll have a look at the driver when I get a spare moment. As I've said
on the upstream ticket, the negative-print bug looks like the thing
lo
Hang on, there might be a problem. That file is from
https://github.com/atondwal/ath10k-firmware and isn't in
https://github.com/kvalo/ath10k-firmware that I can find. So as far as I
know we don't have a license to redistribute that file.
I'll go ahead and inquire with Kalle, hopefully we can get
** Bug watch added: Debian Bug tracker #832432
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832432
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832432
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1605433
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 guessed as much, just making sure. I'll inquire as to why that
board.bin hasn't been pushed out to linux-firmware yet, and as long as
there isn't some reason why we shouldn't I'll pull it into xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
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/1605433
Title:
[Dell Alienware 17R3] enable/disable touchpad not wor
You have been subscribed to a public bug:
The touchpad does not work as expected. It can't be enabled or disabled
through FN+F11 combination.
The light (in the pad) always turns on, regardless of its non
functionality.
The problem seems related to bug #1523738, and some say solution #24
(https:/
possibly. There isn't actually enough information in that bug to be sure
if it is an actual namespacing issue or it is a separate bug to do with
unix domain sockets.
Unfortunately the workaround of attach_disconnect is still required to
deal with these issues.
--
You received this bug notificati
This version is broken.
--
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/1571798
Title:
Broadwell ECRC Support missing in Ubuntu
Status in linux package in Ubuntu:
In Progress
Status in
This is upstream now too.
https://github.com/torvalds/linux/commit/34ee32c9a5696247be405bb0c21f3d1fc6cb5729
--
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/1579984
Title:
Dell dock MAC Ad
Public bug reported:
Ubuntu 14.04 with linux-generic-lts-xenial kernel (4.4.0), running on
Macmini6,2
Installed package bcmwl-kernel-source, which gives me this module for my
wlan0:
# lsmod | grep wl
wl 6365184 0
cfg80211 557056 1 wl
Machine immediately and reli
Yup, but I wanted to avoid getting overwritten each time linux-firmware
gets updated. ;)
--
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/1436940
Title:
Qualcomm Atheros QCA6164 8
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
It looks like it was finally fixed on 4.7.0-040700-generic. I've just
upgraded and for the first time there aren't any call traces in my
dmesg.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
1 - 100 of 168 matches
Mail list logo
