Today, screen corruption didn't happen. I did run an update after it
happened yesterday.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1690528
Title:
screen corruption at startup
To manage not
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1690512
Title:
shutdown/restart/suspend freezes laptop on intel graphic
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 Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1690512
Title:
shutdown/restart/suspend freezes lapto
This is a Kabilake system, the intel-microcode does not support it as of
20161104 or 20170511 (upcoming release, to be uploaded in the next few
days).
Please ensure your BIOS/UEFI is up-to-date, latest known-to-be-available
microcode is revision 0x58, so it is not impossible that there are
availab
Public bug reported:
The Debian version of this package is built for all architectures:
https://buildd.debian.org/status/package.php?p=nvidia-settings
Please do the same for Ubuntu also.
In particular, qtwebengine-opensource-src needs libxnvctrl-dev (which
depends on libxnvctrl0) to build on s3
Explicitly loading the intel driver in xorg.conf and enabling DRI3
appears to have worked around this issue in Chrome/Chromium, using
intel's latest driver distribution.
[ 3026.999] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20160711
[ 3026.999] (II) intel(0): SNA comp
I have made an interesting observation:
When booting disabling IOMMU with amd_iommu=off in the kernel command line the
system seems to work fine yet.
I haven't extensively tested this, but yet I have no crash while creating this
comment, multiple successful reboots, and
$ glxinfo | grep Open
The issue is still exactly the same with Linux kernel 4.12.0-041200rc1
from http://kernel.ubuntu.com/~kernel-ppa/mainline :
* XORG does NOT load its 'nouveau' module.
* Even when I activate my '20-module-nouveau.conf' file to force XORG
to load its 'nouveau' module, this 'nouveau' module does N
Hey Henrique, Thanks for your reply!
I thought kernel 4.10 supported kaby lake CPU's? As I mentioned in the
post, I tried it and it gave even worse results (couldn't get past login
screen)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
*** This bug is a duplicate of bug 1502978 ***
https://bugs.launchpad.net/bugs/1502978
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 1502978, so it is being marked as such. Please look
It is happening in trusty though, which is supported. See several of the
most recent duplicates at the top...
** Changed in: fglrx-installer-updates (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to f
can confirm what others have reported above with 16.04
with 4.4.0-77 I have the issue, the issue wasn't/isn't present with
4.4.0-72 and below
I'm unsure if this problem originates from a Xorg package - from the
most recent Linux Kernel changelogs I think I noticed some bugfix that
could affect th
12 matches
Mail list logo
