I faced the same issue using xubuntu 16.04 (clean installation) after I
installed NVIDIA binary driver - version 340.96 from nvidia-340
(proprietary-tested) instead of X.Org X server - Nouveau (under which no issue
appeared). NVidia driver is more stable so I have to hold it. I edited
@jsalisbury: Yes this issue started after an upgrade and there is a red
Triangle with an exclamation mark inside on my task bar.It tells me the update
information is outdated... and also informs me to update manually. When I
initiate manual update it tell me my system is up-to-date.
Kindly I
er'] failed with exit code 1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP
less extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=
Wildman, if 4.7-rc2 doesn't allow you to test to this problem, please
test successively older kernels until you have the most recent kernel
possible allowing a test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have some stability at now. ))
If I do not use wifi acpi key then I have Wi-Fi and BT after reboot or
sleeping. If I began use it and reboot with BT off then after reboot I can not
switch on BT(only WiFi on/off). Dometimes after using wifi key I can select BT
& WiFi on, widgets on tray say
I tested 4.6.0-rc7-willy kernel maximum. Situation are no changed. Kernel 4.6.1
for yakkety did not start on 16.04.((( I think 4.7rc2 did not start too. I
tested it from http://kernel.ubuntu.com/~kernel-ppa/mainline/
Will I test from kernel.org?
--
You received this bug notification because
Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
9567366fefddeaea4ed1d713270535d93a3b3c76 contains the 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/bugs/1581005
Title:
Dell XPS 15 9550 Freezes when HDMI is plugged in
Status in
I'm working on the bisect now. I already ruled out the suspected commit
- the first bisect step blew right past it. Each build takes about 2.5
hours on an i7-3770 and there's another 10 to go, so I should find the
answer in about about four days or so.
--
You received this bug notification
Since it looks like I am expected to fix this myself, why don't you just
mark it triaged and assign it to me?
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alistair Buxton (a-j-buxton)
--
You received this
"Welcome to the Kafka version of Ubuntu, bye bye to Ubuntu for human beings."
That's bugs.launchpad.net, part of Canonical, for you!
--
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/1566302
** Package changed: ubuntu => bluez (Ubuntu)
--
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/1589889
Title:
Bluetooth search gets nothing on Dell XPS 15 9550
Status in bluez package in
You have been subscribed to a public bug:
Title: Bluetooth search gets nothing on Dell XPS 15 9550
Summary:
Bluetooth search gets nothing on Dell XPS 15 9550
Steps:
1. Open Bluetooth Setting
2. Click "+" to search nearby bluetooth devices
Expected results: BT search could get nearby BT devices
Sure, is there a commit that you think will fix it? (Will try tomorrow
morning.)
--
sent from a rotary phone, pardon my brevity
On Jun 7, 2016 5:05 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
frew, could you please test the latest mainline kernel (4.7-rc2) and
Hrm, something is not quite right with this test box, I'm going to
reimage it. Testing fanatic from ubuntu-fan-0.9.1~fan1 without lxd on
another system is not exhibiting this issue. Marking this Invalid while
I continue to investigate.
** Changed in: ubuntu-fan (Ubuntu)
Status: New =>
Public bug reported:
I was testing fanatic from apw's fan-staging ppa:
ubuntu-fan:
Installed: 0.9.1~fan1
Candidate: 0.9.1~fan1
Version table:
*** 0.9.1~fan1 0
500 http://ppa.launchpad.net/apw/fan-staging/ubuntu/ xenial/main amd64
Packages
100 /var/lib/dpkg/status
Before upgraded to xenial.
when upgraded to xenial,the radeon r7 graphic card can't work.so i
update/upgraded on everday.
then the problem was appear.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
@penalvch good bisect guide! I'll follow it and keep posted which ones
work and which one don't if that's ok
--
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/1580798
Title:
Suspend breaks
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
6
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package: linux (no
ns.
+
+ eno2 no wireless extensions.
+
+ eno1 no wireless extensions.
+ LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
+ MachineType: HP ProLiant BL465c Gen8
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+
6
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package: linux (no
6
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package: linux (no
6
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c Gen8
Package:
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
1:
CasperVersion: 1.376
DistroRelease: Ubuntu 16.10
IwConfig:
lono wireless extensions.
eno2 no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607)
MachineType: HP ProLiant BL465c G
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-rc1
The issue even started happening on the mainline kernel? If so, maybe try the
latest mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc1-yakkety/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed =>
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-rc1
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-rc1
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-rc1
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-rc1
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-rc1
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-rc1
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-rc1
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
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-rc1 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
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-rc1
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-rc1 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
** 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.launchpad.net/bugs/1590072
Title:
kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant
BL465c Gen8 if IOMMU is
** 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.launchpad.net/bugs/1590125
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
16.04
Status in linux
Abhishek Bhatia, in order to allow additional upstream developers to examine
the issue, at your earliest convenience, could you please test the latest
upstream kernel available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one to test
I built the next test kernel, up to the following commit:
a092e19b688be88f7329bd05f90cb92ebe1a4f5b
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
Guntbert Reiter, thank you for reporting this and helping make Ubuntu
better.
As per the release notes from
https://www.asus.com/Motherboards/P8H67V/HelpDesk_Download/ an update to
your computer's buggy, insecure, and outdated BIOS is available (3707).
When you update to this following
monochromec, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585765/comments/6
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
Daniel, please boot into http://cdimage.ubuntu.com/daily-live/current/
and then perform
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590072/comments/4
.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc1-yakkety/ does not
get to boot. It can't find root filing system on SATA SSD.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/ boots
and has the issue. See attached serial console log.
** Attachment added: "Serial Console Log"
Peter Ludwig, regarding your other client, please file a new report (not
post to this closed one).
--
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/1583288
Title:
Realtek Wifi card
Ettore Atalan, to clarify, did you upgrade directly from 12.04 to 16.04
or were you on a different release immediately prior to the upgrade to
16.04?
** Tags removed: needs-full-computer-model
** Tags added: kernel-bug-exists-upstream-4.7-rc2
** Tags added: needs-bisect regression-release
--
$ lspci | grep "00:1c.5" gives
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port
(rev f1)
which seems to the PCI that is failing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Wildman, could you please test the latest mainline kernel (4.7-rc2) and
advise to the results?
** Description changed:
I have Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev
01) on Acer TM B113-E notebook.
When I use ath9k with 3.11 kernel then all works fine. WiFi and
frew, could you please test the latest mainline kernel (4.7-rc2) and
advise to the results?
** Tags removed: bios-outdated-2.37
** Tags added: latest-bios-2.37
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
V B, the next step is to fully commit bisect from the last known good
kernel to the first identified bad one in order to identify the last
good kernel commit, followed immediately by the first bad one. This will
allow for a more expedited analysis of the root cause of your issue.
Could you please
Rudolf Leitgeb, it appears you installed a slightly older version
(1.40), in comparison to the latest (1.42). Could you please advise?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
** 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/1564664
Title:
Peripheral Devices (keyboard and mouse) login delay
xormar, the release names are irrelevant for the purposes of testing.
Regarding the server being in a datacenter, would you have access to its
iLO interface?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
hjl, could you please keep testing successively older kernels from
4.7-rc2 to see if one newer than 4.6-rc4 allows a test?
--
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/1567781
Title:
Uli Köhler, 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
Alistair Buxton, to advise, it doesn't take a build server to test an
upstream commit. Also, that isn't something any one would provide here
on Launchpad.
** Tags added: needs-commit-confirmation-test
** Changed in: linux (Ubuntu)
Importance: Medium => Low
** Changed in: linux (Ubuntu)
raxp, the next step is to fully commit bisect from kernel 3.16 to
3.17-rc1 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following
On checking the syslog(cat /var/log/syslog) I got following output
below. Note that it keeps cumulating and filesize of syslog grows in
~GBs.
Jun 8 05:06:01 hp kernel: [ 1625.694970] pcieport :00:1c.5:[ 0]
Receiver Error
Jun 8 05:06:01 hp kernel: [ 1625.694983] pcieport
Jan Stutzki, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sam, to clarify, do you still need acpi=off to boot?
** Summary changed:
- [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04
+ [MSI GP72 6QE Leopard Pro] acpi=off required to boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi, when removing the WORKAROUND which is editing the /etc/default/grub
to remove pci=nomsi.(The solution suggested.) I get back the same
output(https://launchpadlibrarian.net/263296837/screenshot.jpg) as
before mentioned on the screen after the kubuntu logo on boot.
Please let me know if anymore
Hello
So i do the udpate like this
1)http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/
2a)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb
2b)
Hello
So i do the udpate like this
1)http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/
2a)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb
2b)
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 4.06
S: Manufacturer=Linux 4.6.0-040600-generic ehci_hcd
S: Product=EHCI Host Controller
Public bug reported:
[Impact]
The arm-smmu driver doesn't allow 2 different devices (SMMU 0/1) to share a
namespace. So if 2 devices are connected to same SMMU, it may lead to memory
corruption.
[Test Case]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: High
Assignee: dann
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/1590154
Title:
System slow unless using
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-rc1 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
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-rc1
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
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?
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
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-rc1 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
** 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.launchpad.net/bugs/1587510
Title:
Thinkpad keyboard backlight is not properly restored on resume from
suspend
Status in linux
I built the next test kernel, up to the following commit:
d9dddbf556674bf125ecd925b24e43a5cf2a568a
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1573062
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Public bug reported:
I tested this installing the Disks tool and running a read-only
benchmark. The transfer rate is very slow (2-3 MB/s) unless I'm moving
the cursor, then it jumps up.
As I understand this could have something to do with triggering/handling
interrupts. In this context it might
I could not reproduce the bug under vanilla 4.6.1 with nvidia backports.
The powertop still reports max package C3, no deeper states though.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
> Physical Address Extensions (PAE) 32-bit is available.
If the pae flag is not present in /proc/cpuinfo then PAE is not enabled
on your particular CPU, even if it is available for other CPUs in the
same family. The CPU indicates PAE support (or not) in the result of the
CPUID instruction, which
Sorry, wrong kernel version. The correct version is 4.4.0-22-generic
which came as part of a normal update from the repo.
--
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/1585765
Title:
I've fixed this in Arch Linux by moving to the 4.6.1-2-ARCH kernel, when
previously on the 4.5.? kernel. This problem also doesn't occur in
either the 4.0.7-2 or the 3.16-2 kernels for me at least.
I hear this is happening mostly on the 4.4.0-* kernel, which doesn't
seem to be an option in the
I faced the same issue with an embedded LEX 2I260D-H26 on Ubuntu 16.04
both in kernels 4.6. I faced an issue where (when not blacklisting the
gma500_gfx driver via /etc/modprobe.d/blacklist.conf), the HDMI screen
would stay black, unless the HDMI cable was NOT plugged in during boot
in which case
Hi Christopher,
done and done, thank you for caring :-)
kind regards
guntbert
> Guntbert Reiter, 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
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/1590125
Title:
Middle mouse (wheel-click)
Public bug reported:
The issue looks exactly like #1581088 but I've been asked to file a
separate report.
xev registers buttons 1(left),3(right), 4,5 (scroll wheel), 8,9 (back,
forward), but NOT 2
$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳
Here's a log of me pulling power, and plugging it back in.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "upower.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588944/+attachment/4679103/+files/upower.out
--
You received this
No luck with the Xenial kernel (4.4.0-22), I could repro the crash 2
times (after a couple of hours each). Testing the Wily kernel next.
Here is the relevant part of the logs (both crashes produced near
identical logs):
Jun 07 20:19:44 muchcrash02 kernel: sd 2:0:0:0: Device offlined - not ready
Some data to take into consideration. I've tested 4 difference configs
(3 laptops, 1 server) of mixed Intel and AMD hardware, comparing the
default powersave/ondemand [1] vs performance
[1] depends on CPU and if intel-pstate is supported
For faster modern Intel CPUs where intel-pstate is
** Tags added: kernel-cve-tracking-bug
--
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/1535150
Title:
overlayfs over fuse should refuse copy_up of files if uid/gid not
mapped
Running 4.4.0-23-generic, I see the same errors as
https://bugs.freedesktop.org/show_bug.cgi?id=89055
I see
[ 1248.953987] PM: early resume of devices complete after 6.795 msecs
[ 1248.956059] rtc_cmos 00:02: System wakeup disabled by ACPI
[ 1249.227488] usb 1-8: reset high-speed USB device
I've run these tests now for 24 hours w/o issue on the original kernel
and on my 'fixed' kernel, with no issues in either, so I'm unable to
reproduce this issue. Are there any specific configuration options on
your H/W that I need to try and duplicate as maybe my configuration is
not able to trip
it seems the fix is in proposed according to this page:
https://launchpad.net/ubuntu/+source/linux. But when I enable the
proposed repository the version there is old, so the version on that
page must just be the source version, but the package hasn't actually
been put in the repo?
Clearly I
** Tags added: kernel-cve-tracking-bug
--
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/1547400
Title:
aufs fails to handle sanitize xattrs in workdir, copies SUID binaries
** Tags added: kernel-cve-tracking-bug
--
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/1534961
Title:
insecure overlayfs xattrs handling in copy_up
Status in linux package in
So as I haven't really messed with power monitoring, I discovered upower
--monitor-detail.
After having been unplugged for a few minutes the below state change
occurred. I'm open to advice on how to continue looking into this. My
first guess is to open the upower sources to see where it's
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1578358/+attachment/4679087/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 241 matches
Mail list logo
