I notice that there's no mention of a yakety release. Is that
deliberate?
--
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/1579190
Title:
Key 5 automatically pressed on some Logitech wire
Still happening in yakketi
--
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/1382993
Title:
Micro-sd card not mounted by internal card reader
Status in linux package in Ubuntu:
Confirmed
I just tested 4.7-rc6, the bug is reproduced (system frozen on resume).
--
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/1589379
Title:
System frozen after resume, on Ubuntu 16.04 kernel 4
It took a while but the problem reproduced itself even on 4.4.0-28.
--
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/1582075
Title:
GPU HANG: ecode 6:0:0x85eefffc
Status in linux package
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/vivid/3.19.0-65.73
/vivid-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed in: kernel-sru-workf
Aaron Peromsik, thank you for reporting this and helping make Ubuntu
better.
Given you have confirmed the fix commit via testing, and it was CC'ed to
stable, I'll go ahead and mark this Triaged.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
** Tags added: bios-outdated-f7 cherry-pick
** Description changed:
- [In comments on 1579481 I mentioned that I had found and cherry-picked a
- fix from upstream. I was asked to file another bug so that my hardware
- information could be compared. apport will show kernel version 4.4.0-24
- but t
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-08_04-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Does this bug happen for people after a USB drive has spun down and the
computer tries to access it? My USB freezing issue goes away if I
disable UAS for a particular drive. It works fine with UAS until it
spins down but the USB subsystem freezes when it tries to spin it up,
requiring me to reboot
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/precise/3.2.0-106.147
/precise-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed in: kernel-sru-
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/1600092
Title:
radeon: monitor connected to o
Public bug reported:
[In comments on 1579481 I mentioned that I had found and cherry-picked a
fix from upstream. I was asked to file another bug so that my hardware
information could be compared. apport will show kernel version 4.4.0-24
but the issue is reproducible on 4.4.0-28 as well-- just didn
tests ran: 3, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-08_02-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
With a fresh install of 16.04 on HP 4430s laptop, I have this same issue. BT
worked before I setup my wireless network, and then didn't. I also can confirm
the workaround above of shutting down the laptop, removing power(battery as
well), seems to correct the issue. Fixes tried:
1. uninstalled a
Aaron Peromsik, so your hardware and issue may be scoped, 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.
As I mentioned on 1579481: The commit below (also from upstream) fixes
this for me. Hadn't noticed the one mentioned above... I only cherry-
picked this one on top of current xenial git source. Would be nice to
see this commit find its way into official Xenial kernels.
https://github.com/torvalds/
Confirmed: typing this on my second screen, connected via VGA, after
cherry-picking the commit I linked to in #28. Without that commit the
second screen was recognized but remained dark while connected to the
VGA port of my Kaveri-based desktop. Same monitor had been fine when
connected via DVI.
-
Hello Mathieu, or anyone else affected,
Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.17~16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
Hello Mathieu, or anyone else affected,
Accepted shim-signed into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.17~14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
Hello Mathieu, or anyone else affected,
Accepted shim-signed into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.17~15.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
htt
Hello Mathieu, or anyone else affected,
Accepted shim-signed into precise-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.17~12.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Description changed:
Note: This is different from Launchpad bug #1557151. This is another,
similar, bug.
- This is a very unfortunate bug because the fix only helps you moving
- forward.
-
Bug description from Matt Ahrens at OpenZFS:
"If a ZFS object contains a hole at level one, an
Public bug reported:
Note: This is different from Launchpad bug #1557151. This is another,
similar, bug.
Bug description from Matt Ahrens at OpenZFS:
"If a ZFS object contains a hole at level one, and then a data block is
created at level 0 underneath that l1 block, l0 holes will be created.
Ho
** Changed in: linux (Debian)
Status: Confirmed => 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/1423672
Title:
ext4_mb_generate_buddy:756: group N, block
Chrome flickers... but FF doesn't for me. Are you sure it isn't the
browser.
On Thu, Jul 7, 2016 at 7:58 PM, Thiago Martins
wrote:
> I'm on 4.4.0-28-generic (Xenial), problem still here.
>
> A good website to test it, is TradingView:
>
> https://www.tradingview.com/chart/7ipqeH3N/
>
> Google Chr
I'm on 4.4.0-28-generic (Xenial), problem still here.
A good website to test it, is TradingView:
https://www.tradingview.com/chart/7ipqeH3N/
Google Chrome window flickers a lot! Especially if you really use the
above website, by login in, clicking on its functions, pop-up windows
and etc...
Har
** 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/1574845
Title:
Hardware accelerated video decoding causes GPU crash (
jion, 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.
--
You received this bug
Richard Trabing, 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.
--
You receive
** Also affects: robert (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/443278
Title:
Logitech QuickCam USB webcams using pwc module (
** Tags removed: latest-bios-1.83
** Tags added: bios-outdated-1.86
--
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/1530476
Title:
Lenovo helix 2nd gen does not wake up from suspend
Stat
bhat3, if one thinks they have identified a fix commit, they may test it
via
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
http://lists.infradead.org/pipermail/linux-arm-
kernel/2014-July/274251.html
--
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/1531768
Title:
[arm64] lockups some time after booting
Status
Bit more digging, I see that the CPU goes into idle either by a single
WFI (wait for an interrupt) shallow sleep or a deeper
arm_cpuidle_suspend() - the latter is akin to turning off the CPU. I
wonder if we're seeing some issues with the wakeup latency taking a long
time inside QEMU when the host
The issue has appeared on Ubuntu 16.04 with the 4.4.0-28-generic kernel.
When doing
sudo hdparm -tT /dev/sde
/dev/sde:
Timing cached reads: 8598 MB in 2.00 seconds = 4302.13 MB/sec
Timing buffered disk reads: 56 MB in 3.11 seconds = 18.03 MB/sec
Everything seems fine, but when writing in
Maybe Linux 4.7 adresses the out-of-memory issues with the following
changes:
http://lwn.net/Articles/684945/
https://git.kernel.org/torvalds/c/0a0337e0d1d134465778a16f5cbea95086e8e9e0
https://git.kernel.org/torvalds/c/e28e909c36bb5d6319953822d84df00fce7cbd18
--
You received this bug notificati
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
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/modoc__4.4.0-30.49__2016-07-07_21-39-00/results-index.html
--
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/1597897
I built a Xenial test kernel[0] with the fix[1] suggested in comment
#64. The fix was mentioned upstream[2].
That particular patch has not landed in mainline yet, but it was also
cc'd to stable for all 4.4+ kernels.
This commit can be added as a SAUCE patch if we find that it resolves
this bug,
On an idle Xenial cloud image I'm seeing:
[ 1485.236760] [] __switch_to+0x90/0xa8
[ 1485.236772] [] __tick_nohz_idle_enter+0x50/0x3f0
[ 1485.236776] [] tick_nohz_idle_enter+0x40/0x70
[ 1485.236785] [] cpu_startup_entry+0x288/0x2d8
[ 1485.236791] [] secondary_start_kernel+0x120/0x130
[ 1485.236795]
I'm sorry, but there's no way I can do 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/1580311
Title:
Laptop panel output only if external display connected
Status in linux package
** No longer affects: linux (Ubuntu Wily)
--
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/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in lin
** Changed in: linux (Ubuntu Wily)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Christopher,
I installed some of vdpau packages which was missing in 12.04. Which one
exactly - I do not remember. If it is important and could be traced in
log files - please give me a hint.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
Oh, and an important comment.. this bug happens to me in Ubuntu 14.04,
16.04, with unity and with kde (with unity the issue comes faster than
with kde)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I experience this bug all the time from at least 2 years. The issue
started for me when I switch to 64bits ubuntu version. I'm a web
developer and chrome is the main cause of this issue. Ubuntu starts to
swap and all freezes until the application that is causing this stops or
turn idle. CTRL+ALT+Fx
tests ran: 20, failed: 7;
http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_20-19-00/results-index.html
--
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/1597053
Christopher,
Please find the post in the mailing list below
http://thread.gmane.org/gmane.linux.usb.general/144630/focus=144635
--
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/1534948
Titl
Answer from asrock...
i think that this is more of an issue with the Kernel. I can ask the engineers
to look into it but as this OS is not on the tested list this does not warranty
an rma.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Same issue with the folowing BT headphones:
* Plantronic BackBeat FIT.
* Plantronic BackBeat PRO.
* B&O Beoplay H8.
The computer has a BT USB dongle:
Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
CSR8510 A10
USB ID = 0a12:0001
The following procedure solved the problem for
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-07_19-08-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
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/1447485
Title:
serial: 8250_pci: Add support for 16 port E
Started run on 3.14-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/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
Status in linux packag
tests ran: 18, failed: 3;
http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_19-36-00/results-index.html
--
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/1597053
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_18-40-00/results-index.html
--
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/1597053
Christopher, want to see if there is an additional failure after removing an
autostart desktop file. The journal indicates a problem in gnome-session and
indeed gsm-manager.c issues the failure message
"WARNING: Application 'at-spi-dbus-bus.desktop' failed to register before
timeout" after a 9
Exactly the same (and some more) problems are on my Lenovo X250
Broadwell machine with 4.4 kernel. I have tested 4.6.0, 4.6.3 and just
now 4.7-rc6. All issues disapeared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Thanks guys, I really think the solution here will be to move onto the
lts-xenial kernel as all others lts- kernels will be end of life
shortly.
--
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
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/1599951
Title:
On read_tsc function issue.
S
Public bug reported:
Below is result of perf report:
read_tsc /proc/kcore
│
│
│
│Disassembly of section load0:
│
│81037780 :
66,67 │ push
Here's the log from running `sudo unattended-upgrade --dry-run --debug`
in case it's helpful:
2016-07-07 16:58:53,281 INFO Initial blacklisted packages:
2016-07-07 16:58:53,282 INFO Starting unattended upgrades script
2016-07-07 16:58:53,282 INFO Allowed origins are:
['o=Ubuntu,a=precise-security
tests ran: 20, failed: 7;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_17-08-00/results-index.html
--
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/159663
** Summary changed:
- [FFe] ZFS pools should be automatically scrubbed
+ ZFS pools should be automatically scrubbed
--
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/1548009
Title:
ZFS
Joseph,
Shotwell seems to be working across 3 Ubuntu machines now. Sometimes I
get a false-negative warning about the system not claiming the
device...but then the camera shows up somewhere else.
I think I'll skip the Upstream Kernel Test for now.
Thanks,
Richard
Time, upgrades & updates seem
tests ran: 18, failed: 3;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_16-23-00/results-index.html
--
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/159663
** Description changed:
To avoid git repo tag namespace collisions, the derivative kernel target
names should be embedded in their git 'release' tags, e.g. in the Ubuntu
Xenial git repo:
tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23
tag Ubuntu-snapdragon-4.4.
Public bug reported:
To avoid git repo tag namespace collisions, the derivative kernel target
names should be embedded in their git 'release' tags, e.g. in the Ubuntu
Xenial git repo:
tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23
tag Ubuntu-snapdragon-4.4.0-1020.23 inst
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_15-34-00/results-index.html
--
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/159663
Hi, I just wanted to keep this thread alive, as the bug seems still to be
present. I recently tried suspend with the Helix 2 and Ubuntu 16.04 and can
confirm the same behaviour.
This issue is being tracked on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=100171
There was a BIOS
I've restored the data and all kernels from Ubuntu-3.13.0-91.138 through
to the latest upstream v4.7-rc6 can attempt to mount the restored data
without oopsing the kernel. However, the data I have is definitely
broken and cannot be mounted, even btrfs-image -r on the image reports
a transid failu
Joseph,
thank you for your reply.
All the tests I've made were done starting from fresh install.
The issue persist on 4.7.0-040700rc6-generic (X64): at least 10 seconds before
have the keyboard working again.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: k
Thank you Joseph, I will test v4.7-rc6 mainline build.
This is another first for me, so I need some time to learn this, plus I
will set up and install Ubuntu 16.04 on a different machine to avoid
risks, and test the bug on another computer. Hopefully I will have this
all done within 24-48 hours.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_14-42-00/results-index.html
--
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/159663
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Precise)
Status: In
hi again Christopher,
Found some time to test various kernels as indicated. Here are the
results in correct chronological order:
0) 15.10 / kernel 4.2.0: last known good configuration
1) 16.04 / kernel 4.4.0: error found, bug reported
then tested:
2) v4.6-rc7-wily / 4.6.0: works as expected
3) v4
To perform a reverse bisect, we need to identify the last bad kernel
version and the first good one. We know that 4.4.14 is bad and 4.6
final is good.
Can you next test the upstream 4.5. kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
If it is also go
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
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
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
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
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
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
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
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
The commit that fixes this bug, may have introduced bug 1598197
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Gavin Guo (mimi0213kimo)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
** Tags added: kernel-da-key
** Changed in: linux-lts-trusty (Ubuntu)
Importance: Undecided => High
** Package changed: linux-lts-trusty (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
S
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
** Tags added: bot-stop-nagging
** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu)
** Changed in: ubuntu-touch-meta (Ubuntu)
Importance: Medium => Undecided
** Changed in: ubuntu-touc
** Tags added: bot-stop-nagging
** Tags added: kernel-da-key
** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu)
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is su
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
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
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 148 matches
Mail list logo
