** Description changed:
The laptop is thinkpad, and when I use testing version of Ubuntu 18.04,
close the lip, and then unable to wake up the linux session again. The
screen is fully black.
I found it not a bug from any desktop session managers because all
desktop environments
I just confirm this bug is from ubuntu kernel 4.13 since I force install
xenial kernel 4.4 on Ubuntu 18.04 and everything is fixed. So I think
there is some problem from nouveau driver.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
What kind of else information do you need?
--
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/1741735
Title:
Laptop Wake-up bug from Current Ubuntu 18.04 Kernel
Status in linux package in
No Error reported from apport even closing the lip and reboot so I have
to manually post some infomation of this bug.
$ lsusb
Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications
Processor
Bus 002 Device 003: ID 04ca:0061 Lite-On Technology Corp.
Bus 002 Device 002: ID
Public bug reported:
The laptop is thinkpad, and when I use testing version of Ubuntu 18.04,
close the lip, and then unable to wake up the linux session again. The
screen is fully black.
I found it not a bug from any desktop session managers because all
desktop environments (openbox/mate) will
Public bug reported:
When using ubuntu-mate or ubuntu-flashback, all of which is based on
marco/metacity, there is a small possibilty for ubuntu mate/flashback desktop
to be screen blurred "for its first start" in Virtualbox. But after executing
"service lightdm restart" in tty1, it will be
So I think there is still bug about memory.kmem.limit_in_bytes.
If I don't limit the kmem of lxc container at the beginning,
"memory.limit_in_bytes" can be set to zero by the above step.
If I limit the kmem of lxc container at the beginning,
"memory.limit_in_bytes" cannot be set to zero, also
Previously, I am always thinking the following:
1) memory.usage_in_bytes = memory.kmem.usage_in_bytes + "Non-Kernel
Memory Data"
2) the data of "memory.kmem.usage_in_bytes" cannot be moved to swap
which indicates that memory.usage_in_bytes should be always >0 since
memory.kmem.usage_in_bytes
Thanks, but a strange thing is that lxc performs different from docker.
Can you try the following?
# sudo -i
# lxc-start -n ubuntu1
# echo 1g > /sys/fs/cgroup/memory/lxc/ubuntu1/memory.limit_in_bytes
# echo 1g > /sys/fs/cgroup/memory/lxc/ubuntu1/memory.memsw.limit_in_bytes
# lxc-freeze -n
Sorry, "not after executing docker with" should be "only after executing
docker with"
--
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/1568592
Title:
bug of "memory.kmem.limit_in_bytes"
Hi, after full upgrade, "memory.kmem.limit_in_bytes" and
"memory.kmem.usage_in_bytes" works not after executing docker with
"--kernel-memory" argument.
--
But if you run a command like "docker run -it --rm ubuntu bash" without
--kernel-memory argument,
are you able to get the correct value of
This bug is critical because docker 1.10 will crash when running "docker
run --kernel-memory 1G ubuntu bash"
--
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/1568592
Title:
bug of
Just a fresh installation from "http://cdimage.ubuntu.com/daily-
live/current/xenial-desktop-amd64.iso" will definitly have this issue,
not my PC's problem.
After installing "http://cdimage.ubuntu.com/daily-live/current/xenial-
desktop-amd64.iso",
# echo 10 >
Public bug reported:
In ubuntuxenial with linux kernel 4.4,
"memory.kmem.limit_in_bytes" cannot be written,
and the value of "memory.kmem.usage_in_bytes" is always 0.
This issue doesn't happen in ubuntu wily (kernel = 4.2)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
Thanks for the explaination!
--
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/1559725
Title:
Security bug of overlayfs in linux image kernel
Status in linux package in Ubuntu:
Invalid
Hi, because ubuntu xenial just upgrade its linux kernel to 4.4-2, I
tested this bug and it still happends.
--
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/1537465
Title:
Idle too much
If I don't blacklist snd-usb-audio, 50s delay will be inserted bewteen
"lightdm login" and "show session desktop".
** Attachment added: "2016-02-02 20-02-28.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537465/+attachment/4562081/+files/2016-02-02%2020-02-28.png
--
You received
Public bug reported:
I'm using Ubuntu 16.04 amd64 Desktop, with kernel 4.3. And my USB Video
Camera is from Gsou, containing both camera device and microphone
device.
When booting Ubuntu, after login ubuntu session, system freeze for
around 40 seconds !!
Finnally I found out that its
18 matches
Mail list logo
